GitHub Bounties💵 paid workby tristanworkscored by google/gemini-2.5-flash

SecureBananaLabs/bug-bounty: Freelancer profile should render matching mock profile and unknown fallback

Visit project ↗Discussion ↗

💵 Funded work— see “Deliver it” below for how to respond.

Opportunity

AI-buildable

Traction

Creativity

The take

effort: ~weekend

This is a bounty to fix a bug in a web application where freelancer profile pages do not correctly render data from a mock file. Currently, the pages show generic placeholder text for both known and unknown usernames. The task is to ensure known usernames display mock profile details and unknown usernames show a not-found page.

Demand & gap

Painkillerdemand 76

Demand

Will. to pay

Gap

Buyer

Developers

The gap in what exists: The gap is simply the unmet need for this specific bug to be fixed, as indicated by the bounty payment.
Wedge to win: Deliver a robust, tested fix quickly to claim the bounty payment.
Reputation value (worth doing free for proof) — 70/100: A successful bounty completion and merged PR to this repository would be concrete proof of ability to quickly diagnose and fix issues in unfamiliar Next.js codebases, enhancing credibility for freelance dev work.
Likely monetization: one-off bounty payment

Deliver it

A starter prompt for Claude Code, what you'll need, and how to reach them.

You are an expert Next.js developer. The goal is to fix a bug in the SecureBananaLabs/bug-bounty repository, specifically issue #2763. The `/freelancers/[username]` route in `apps/web` incorrectly displays placeholder text instead of dynamic mock profile data. Fork the repository and implement the following: 1. In `apps/web/src/app/freelancers/[username]/page.tsx` (or equivalent file handling the route), retrieve the `username` from the route parameters. 2. Import the mock freelancer data from `apps/web/lib/mock.ts`. 3. Implement logic to search for a freelancer matching the `username` in the mock data. 4. If a match is found, render the profile page with the freelancer's actual skills and hourly rate from the mock data. 5. If no match is found for the `username`, render a clear 'not found' fallback component (e.g., 'Freelancer not found'). 6. Ensure the UI components dynamically display the mock data fields like `skills` and `hourlyRate` where appropriate. Use Next.js 16 App Router, React 19, and Tailwind v4 principles. Provide the corrected code for the relevant file(s) and any new components.

Prerequisites — cost & what to learn

GitHub accountFree · Free

How you'd build it

1Clone the SecureBananaLabs/bug-bounty repository.
2Identify the `/freelancers/[username]` route handler in `apps/web`.
3Implement logic to read `username` from the URL and query `apps/web/lib/mock.ts` for matching freelancer data.
4Conditionally render either the freelancer's details using the mock data or a 'not found' component if no match is found.
5Ensure the displayed skills and hourly rate match the mock data structure.
6Submit a pull request with the fix.

Risks & moats

Understanding the existing codebase and data structure might take longer than anticipated.
The mock data file might have an unexpected structure or be difficult to parse.
Integrating the fix cleanly into the existing Next.js application structure might require minor refactoring.
The bounty issuer's review process could be slow or require multiple iterations.

Original context

Bounty (amount on the issue). Parent bounty: #743 ## Bug The `/freelancers/[username]` route currently renders placeholder text with the requested username instead of looking up the selected freelancer from `apps/web/lib/mock.ts`. Search cards link to `/freelancers/maya-dev` and `/freelancers/jordan-ux`, but the profile page does not show the matching skills or hourly rate. Unknown usernames also appear successful. ## Expected - Known freelancer usernames render the matching mock profile details. - The profile page exposes useful skills/rate context instead of generic placeholder copy. - Unknown usernames render a clear not-found fallback. ## Scope Keep the fix limited to the web freelancer profile route unless the existing mock data needs a minimal shape adjustment.