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

SecureBananaLabs/bug-bounty: Job detail page should render matching mock job 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 job detail page. The `/jobs/[id]` route incorrectly renders placeholder text instead of dynamic job data from a mock file. The task involves ensuring known job IDs display correct details and unknown IDs show a proper 'not found' fallback.

Demand & gap

Painkillerdemand 88

Demand

Will. to pay

Gap

Buyer

Developers

The gap in what exists: The original project has a clear bug that needs to be fixed, and they've put a bounty on it, indicating a gap in their current development capacity for this specific task.
Wedge to win: Deliver a precise, tested fix for the specified bounty requirements quickly.
Reputation value (worth doing free for proof) — 80/100: A successful, merged PR to a public bounty project demonstrates direct coding ability and problem-solving skills, valuable for securing future freelance development contracts or showcasing expertise.
Likely monetization: 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 16 App Router, React 19, Tailwind v4, and Node.js developer. I need to complete a GitHub bounty from SecureBananaLabs/bug-bounty, specifically issue #2755, which is titled 'Job detail page should render matching mock job and unknown fallback'. Your task is to implement the fix for the `/jobs/[id]` route in the `apps/web/` directory. First, fork the SecureBananaLabs/bug-bounty repository. Identify the component responsible for rendering the job detail page. Then, implement logic to read the `id` from the route parameters. Use this `id` to look up the corresponding job details (title, budget, etc.) from `apps/web/lib/mock.ts`. If a matching job is found, render its specific details dynamically on the page. If no job matches the `id`, display a clear 'Job Not Found' message. Ensure the solution adheres strictly to the scope described in the bounty, keeping changes limited to the web job detail route and potentially adjusting the mock data shape if absolutely necessary. Provide the necessary code changes within the context of the existing project structure.

Prerequisites — cost & what to learn

GitHub accountFree · Free

How you'd build it

1Fork the SecureBananaLabs/bug-bounty repository.
2Identify the `[id]` route component for job details in `apps/web/`.
3Implement logic to fetch job data from `apps/web/lib/mock.ts` based on the `id` parameter.
4Render the retrieved job title and budget dynamically.
5Add a conditional render for a 'not found' message if the `id` does not match any mock job.
6Submit a pull request to the original repository.

Risks & moats

Understanding the existing codebase structure and `mock.ts` data shape quickly.
Potential for unforeseen edge cases in ID parsing or data lookup.
Ensuring the fix is strictly limited to the specified scope without introducing regressions.

Original context

Bounty (amount on the issue). Parent bounty: #743 ## Bug The `/jobs/[id]` route currently renders the requested route id as placeholder text instead of looking up the selected job from `apps/web/lib/mock.ts`. Existing job cards link to `/jobs/job-101`, `/jobs/job-102`, and `/jobs/job-103`, but the detail page does not show the matching job title or budget. Unknown job ids also look successful, which gives clients no clear fallback. ## Expected - Known job ids render the matching mock job title and budget. - The detail page exposes useful project context instead of generic placeholder copy. - Unknown job ids render a clear not-found fallback without pretending a real job exists. ## Scope Keep the fix limited to the web job detail route and mock data shape if needed.