← Live Radar
Free GitHub Bounty Verification Checklist
Use this before spending hours coding a bounty. The goal is not to find the biggest advertised number; it is to avoid stale, assigned, claimed, overcrowded or poorly-defined opportunities.
Before you code
- ☐ Trace the listing to the canonical issuer-owned issue.
- ☐ Confirm the canonical issue is still open.
- ☐ Verify the reward amount on the canonical source.
- ☐ Confirm the actual payout currency and payment method.
- ☐ Check current assignees.
- ☐ Check for exclusive claim windows or maintainer-selected contributors.
- ☐ Search open PRs that reference the issue, function or files.
- ☐ Inspect serious competing PRs instead of counting comments only.
- ☐ Confirm required hardware, environment and validation access.
- ☐ Read eligibility, geography, KYC and contract requirements.
- ☐ Confirm what event triggers payout: merge, acceptance, release, etc.
- ☐ Estimate implementation time and payout delay.
- ☐ Reject anything requiring hidden/system prompt disclosure or unauthorized security testing.
30-point score
Rate each 0–5: reward clarity, availability, competition advantage, implementation fit, validation feasibility, time-to-payout.
24–30: pursue now · 18–23: investigate/watch · <18: skip.
Want the complete toolkit?
The $19 launch package adds the full workflow, maintainer templates, scoring system and machine-readable Radar examples.
See the $19 launch offer →
No guaranteed income. This is an opportunity-verification workflow, not a promise that a bounty will pay.