<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Bounty Filter</title>
    <description>The latest articles on DEV Community by Bounty Filter (@realbountyfilter).</description>
    <link>https://dev.to/realbountyfilter</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4256128%2Fe76bbf27-6965-40e4-bd2b-416fd8158d38.jpg</url>
      <title>DEV Community: Bounty Filter</title>
      <link>https://dev.to/realbountyfilter</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/realbountyfilter"/>
    <language>en</language>
    <item>
      <title>I scanned 430 open GitHub "bounty" issues. 311 were spam.</title>
      <dc:creator>Bounty Filter</dc:creator>
      <pubDate>Fri, 20 Nov 2026 17:24:16 +0000</pubDate>
      <link>https://dev.to/realbountyfilter/i-scanned-430-open-github-bounty-issues-311-were-spam-7kf</link>
      <guid>https://dev.to/realbountyfilter/i-scanned-430-open-github-bounty-issues-311-were-spam-7kf</guid>
      <description>&lt;p&gt;I wanted to earn a first open-source bounty, so I pulled every open GitHub issue I could find with a bounty label or an Algora bot comment and looked at what was actually there.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I found
&lt;/h2&gt;

&lt;p&gt;Out of 430 open issues:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;290 came from just 13 repos&lt;/strong&gt; that mass-post "bounties" (one had hundreds of open bounty issues and was a month old).&lt;/li&gt;
&lt;li&gt;Most of the rest sat on repos with 0-2 stars, or repos created in the last two months, often promising USDC.&lt;/li&gt;
&lt;li&gt;3 had already been paid out but were never closed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Only 22 were on established projects.&lt;/strong&gt; 94 more I could not check before hitting GitHub's API rate limit.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And the real ones are crowded. Some examples from the 22:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A $50 bounty with 52 people attempting it and 13 pull requests already claiming it.&lt;/li&gt;
&lt;li&gt;A $5 bounty with 14 attempts and 4 claims.&lt;/li&gt;
&lt;li&gt;A $25 feature request with 12 attempts since June and nothing merged.&lt;/li&gt;
&lt;li&gt;At the other end, a $2,340 bounty (WearOS support for microG) with only 2 attempts, because it is genuinely hard.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;My takeaway: the label search is nearly useless on its own. Check the repo's age and stars, then count the &lt;code&gt;/attempt&lt;/code&gt; and &lt;code&gt;/claim&lt;/code&gt; comments before writing a line of code.&lt;/p&gt;

&lt;h2&gt;
  
  
  The list
&lt;/h2&gt;

&lt;p&gt;I put the filtered list online with a 0-100 score for each bounty and a plain note on how crowded it is:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://real-bounty-filter.vercel.app" rel="noopener noreferrer"&gt;https://real-bounty-filter.vercel.app&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The top 5 are free. The full list of 22, the rejected repos with the reason for each, and a CSV are CA$3.&lt;/p&gt;

&lt;p&gt;Honest caveats: it is a manual snapshot from 20 November 2026 rather than live data, and bounty amounts are parsed from issue text so verify on the issue before you start.&lt;/p&gt;

&lt;p&gt;If you hunt bounties, I would like to know what signals you use to decide one is worth your time.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>github</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
