wtf is bounty-check?

bounty-check is a small command line tool that answers one question: is this GitHub bounty issue actually still claimable? The author explains that they spent close to an hour manually checking bounty listings on sites like Algora and IssueHunt, only to find that most were already dead in ways the listing itself never showed, such as the issue being closed, the repository being archived so a pull request could never merge, or someone else already having an open pull request against it. You point the tool at a GitHub issue URL, an IssueHunt link, an Opire link, or a short owner/repo#123 form, and it uses GitHub's own API to check whether the issue is genuinely open, whether the repository has been archived, and whether an open pull request already references that issue. It resolves Opire's opaque listing URLs by reading the real GitHub issue link off Opire's page first, without needing an Opire API key. You can also scan every open, bounty labeled issue across a whole repository at once, and results can be printed as machine readable JSON. The tool reports one of a few outcomes: ARCHIVED_REPO if the repo cannot accept a merge, CLOSED if the issue is already resolved, HAS_OPEN_PR if someone is already ahead of you, or OPEN_CLAIMABLE otherwise, with a note if the repository has not been pushed to in over two years. The README is honest that a clean OPEN_CLAIMABLE result is not a guarantee, since popular bounty issues can attract many competing pull requests within hours of being posted. It does not judge whether an issue is well scoped or worth the reward, that part still needs a human read of the issue. Adding a GitHub token raises the API rate limit from 60 requests per hour to 5000, which matters if checking many issues at once. The test suite runs entirely against mocked API responses, so no network access or token is needed to run it. The project is released under the MIT license.