← Blog · Nov 10, 2026

GitHub bounty checklist: 6 checks before you start

Before you spend hours on a GitHub bounty, run this checklist. Each step rules out a common way to waste time.

  1. Platform confirmation. Look for the platform's own signal: the algora-pbc comment (Algora), bountyhub-bot (BountyHub), the taskbounty label (TaskBounty), or the reward in Opire's public API. A typed "/bounty $500" is not confirmation.
  2. Open and unassigned. If the issue is closed or someone is already assigned, move on.
  3. No merged pull request. Check the issue's linked and cross-referenced pull requests. If one has already been merged, the work is done.
  4. Count the competition. Several open pull requests (three or more is a crowded issue) means the odds of being the one merged are low.
  5. Check the repository. Is it archived, inactive for months, brand new, or does the owner propose bounties on their own project? Each is a risk signal.
  6. Read the contributing guide and say you are working on it. Some maintainers want an assignment before a pull request, and a pull request that ignores the project's rules is usually closed.

The free bounty verifier automates steps 1 to 5: paste an issue URL and it returns a verdict (real and workable, real but risky, real but not available, or not confirmed) with the evidence. It does not replace step 6, and it cannot check IssueHunt bounties.

For the manual method, see how to spot fake GitHub bounties and how to claim an Algora bounty.

FAQ

What should I check before working on a GitHub bounty? That the platform itself confirms the bounty, that the issue is open and unassigned, that no merged pull request already solves it, how many pull requests compete, and that the repository is active and trustworthy.

How many competing pull requests is too many? There is no fixed rule, but three or more open pull requests on the same issue usually means a crowded bounty where your chances of being merged are low.

Is there a tool that checks a GitHub bounty for me? Yes. The free BountyOS verifier takes an issue URL and checks platform confirmation, assignment, merged pull requests, competition and repository health. It cannot check IssueHunt bounties.