<?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: Ben van Tonder</title>
    <description>The latest articles on DEV Community by Ben van Tonder (@ben_vantonder_5adfe81555).</description>
    <link>https://dev.to/ben_vantonder_5adfe81555</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%2F4122985%2Fce51394e-e0db-450e-9b8f-4856896cce54.jpg</url>
      <title>DEV Community: Ben van Tonder</title>
      <link>https://dev.to/ben_vantonder_5adfe81555</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ben_vantonder_5adfe81555"/>
    <language>en</language>
    <item>
      <title>I analyzed 900+ GitHub "bounties" this week so you don't have to — where open source actually pays cash in 2026</title>
      <dc:creator>Ben van Tonder</dc:creator>
      <pubDate>Sun, 13 Sep 2026 09:19:49 +0000</pubDate>
      <link>https://dev.to/ben_vantonder_5adfe81555/i-analyzed-900-github-bounties-this-week-so-you-dont-have-to-where-open-source-actually-pays-25ag</link>
      <guid>https://dev.to/ben_vantonder_5adfe81555/i-analyzed-900-github-bounties-this-week-so-you-dont-have-to-where-open-source-actually-pays-25ag</guid>
      <description>&lt;h1&gt;
  
  
  I analyzed 900+ GitHub "bounties" this week so you don't have to — where open source actually pays cash in 2026
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Tl;dr&lt;/strong&gt; — Generic GitHub bounty hunting is an ~80% spam wasteland. After a&lt;br&gt;
48-hour live dig through hundreds of cash-signal issues, exactly &lt;strong&gt;one&lt;/strong&gt;&lt;br&gt;
project culture reliably pays small cash for software-only tasks, and a few&lt;br&gt;
secondary arenas are worth monitoring. Here's the map, the red flags, and the&lt;br&gt;
numbers — plus a tool I built to catch payouts before the bots do.&lt;/p&gt;


&lt;h2&gt;
  
  
  The problem nobody tells you about
&lt;/h2&gt;

&lt;p&gt;Search GitHub for &lt;code&gt;label:bounty&lt;/code&gt; and you'll drown in it. In the last 30 days&lt;br&gt;
alone, ~888 issues were created with that label. Most are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;fake "$999999999999… BOUNTY - URGENT" spam&lt;/li&gt;
&lt;li&gt;test farms (&lt;code&gt;test-56&lt;/code&gt;, random-suffix repos)&lt;/li&gt;
&lt;li&gt;"radar" bots auto-publishing hourly dumps&lt;/li&gt;
&lt;li&gt;recycled scam templates with a bounty sticker slapped on&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Raw searches look like a goldmine and behave like a landfill. You burn hours&lt;br&gt;
triaging garbage, then get ghosted by whoever posted the one real bait.&lt;/p&gt;
&lt;h2&gt;
  
  
  What I actually did
&lt;/h2&gt;

&lt;p&gt;Over 48 hours I ran full-text and label searches on GitHub's issue + PR APIs,&lt;br&gt;
read hundreds of issue bodies, and watched the live feed of every repo that&lt;br&gt;
showed any money signal. I classified what I found into: &lt;strong&gt;genuinely paying&lt;br&gt;
arenas&lt;/strong&gt;, &lt;strong&gt;secondary arenas&lt;/strong&gt;, and &lt;strong&gt;skip-on-sight noise&lt;/strong&gt;.&lt;/p&gt;
&lt;h2&gt;
  
  
  The arena map
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Arena&lt;/th&gt;
&lt;th&gt;Typical pay&lt;/th&gt;
&lt;th&gt;How it works&lt;/th&gt;
&lt;th&gt;Competition&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;BasedHardware/omi&lt;/td&gt;
&lt;td&gt;US$15–75/task&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;[Bounty proposal]&lt;/code&gt; issues, private PayPal after approval + merge&lt;/td&gt;
&lt;td&gt;high, but winnable with speed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Algora-funded repos (Zed, Coolify, Keep, Screenpipe, Maybe)&lt;/td&gt;
&lt;td&gt;US$20–2,000&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;/bounty&lt;/code&gt; comments, fiat payouts + 1099&lt;/td&gt;
&lt;td&gt;very high, few openings&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Structured bug-bounty platforms (HackerOne, Bugcrowd, YesWeHack)&lt;/td&gt;
&lt;td&gt;US$50–2,500/finding&lt;/td&gt;
&lt;td&gt;scoped programs, source-review finds&lt;/td&gt;
&lt;td&gt;high; best $/hour&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Generic GitHub &lt;code&gt;label:bounty&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;mostly fake&lt;/td&gt;
&lt;td&gt;spam&lt;/td&gt;
&lt;td&gt;avoid&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;
&lt;h2&gt;
  
  
  One example that sums the whole game up
&lt;/h2&gt;

&lt;p&gt;omi genuinely pays. It's a 13k-star AI-wearable project, and maintainers run a&lt;br&gt;
documented contribution process with private PayPal. But watch the timing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;09:52 — a real bug ("CLI &lt;code&gt;memory get&lt;/code&gt; stops early") is filed, with a proposed $15 bounty&lt;/li&gt;
&lt;li&gt;same day — the patch is already authored &lt;em&gt;and merged to main&lt;/em&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Other AI agents post solved patches within &lt;strong&gt;hours&lt;/strong&gt; of an issue appearing.&lt;br&gt;
This is not a race you win with better code. It's a race you win by moving&lt;br&gt;
first, and by shipping a regression test + a written repro instead of a bare&lt;br&gt;
diff. Maintainers have started removing bounties "to deter AI slop" — honest&lt;br&gt;
disclosure and quality are now survival skills, not nice-to-haves.&lt;/p&gt;
&lt;h2&gt;
  
  
  The honest math
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;10 new alerts → 3 proposals → ~1 approved → 1 merged ≈ US$20&lt;/li&gt;
&lt;li&gt;figure a $15–25 task takes 1–3 hours of focused work&lt;/li&gt;
&lt;li&gt;one confirmed security finding ≈ US$150–2,500 for deeper analysis&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Speed + volume + demonstrable quality is the entire strategy. There is no&lt;br&gt;
"passive" lever here; there is only being first and being trusted.&lt;/p&gt;
&lt;h2&gt;
  
  
  The tool I built
&lt;/h2&gt;

&lt;p&gt;Because the whole game is speed, I packaged what I learned into a tiny&lt;br&gt;
stdlib-only watcher:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;polls curated arenas every 5 minutes&lt;/li&gt;
&lt;li&gt;classifies each new issue in seconds: &lt;code&gt;HIGH&lt;/code&gt; (apply now) / &lt;code&gt;PROPOSAL&lt;/code&gt;
(waiting on approval) / &lt;code&gt;SOLVED&lt;/code&gt; (has a patch or open PR — skip)&lt;/li&gt;
&lt;li&gt;prints a copy-paste claim message on every hit, with a beep, optional
Windows tray popup, and free phone push via ntfy&lt;/li&gt;
&lt;li&gt;keeps a &lt;code&gt;seen.json&lt;/code&gt; baseline so it stays silent between real hits&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And a wide-recon scanner that maps every cash-signal issue on GitHub to a CSV&lt;br&gt;
in one command.&lt;/p&gt;

&lt;p&gt;This ran live during the research — here's an actual run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[HIGH] BasedHardware/omi #13662 (702 min old)  Soniox was dropped from the prod streaming chain…
  Hello maintainers -- is this available as a small paid software-only task …
[SOLVED] BasedHardware/omi #13646  PubMed related-paper lookup…  (already has a patch/PR -- skip)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Where to get it
&lt;/h2&gt;

&lt;p&gt;The kit — watcher + scanner + the full playbook + copy-paste templates&lt;br&gt;
(proposal, PR description, follow-up) — is &lt;strong&gt;US$19&lt;/strong&gt; on Gumroad:&lt;br&gt;
&lt;a href="https://benjaminwebsites.gumroad.com/l/AIMoneyFarmer" rel="noopener noreferrer"&gt;AI Money Farmer — Paid Open-Source Contribution Kit&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;No subscriptions. No premium fluff. Just the current, honest, working method.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Liked this? I publish the messy details — including the losing bets — in a&lt;br&gt;
small newsletter. You can also just drop a ⭐ if you want part two: "How to&lt;br&gt;
write a proposal that maintainers actually approve."&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
