Fetching from the wire…
Public story · 2026-07-21 · high
The last $10 million took five months to raise, down from nearly two years for the first, as corporate sponsorships pull ahead of individual ones.
Why now: GitHub published the milestone on July 21, the same day it disclosed the acceleration curve and the org-versus-individual funding split behind the $100 million total.
GitHub Sponsors has paid open source maintainers more than $100 million since launch, GitHub said July 21. GitHub's own post names maintainer burnout as one of the biggest risks to the software supply chain, and admits the funding gap remains enormous.
That money reaches more than 70,000 maintainers and organizations in 103 regions, funded by over 280,000 sponsors, according to GitHub's post. Split across those 70,000 accounts, $100 million comes to roughly $1,400 each, spread over years, not annually.
The post doesn't say how evenly that money is spread. A milestone total can hide plenty of maintainers getting next to nothing.
The curve is what stands out. The first $10 million took nearly two years to raise. The most recent: five months, a sharp jump in pace for the same program.
That acceleration tracks who's funding it. Organization-funded sponsorships average close to 15 times the value of individual ones, GitHub says, and corporate money is what's pulling the growth curve forward.
Watch the org-to-individual ratio from here. If corporate sponsorships keep growing at 15 times the individual rate, funding tilts further toward companies. The maintainers who get paid will increasingly be the ones whose users are companies, not hobbyists.
Each link below shares sources, entities, or timing with this story.
GitHub shipped it July 28 across Pro through Enterprise, reachable from VS Code, Visual Studio, Copilot CLI, the cloud agent, JetBrains, Xcode, and Eclipse, with text and image inputs and low/medium/high reasoning effort, billed at provider list pricing rather than a fixed mul...
K3's weights have been public since late July and it is the largest open-weight model in the world, yet the local runtimes only just caught up while GitHub shipped K3 to every Copilot tier this week (GitHub Changelog). The old open-weights story has inverted. The hosted path i...
The August 13 availability report covers eight incidents. July 8 ran 7 hours 4 minutes at ~96% error rate across Web UI, REST/GraphQL, Actions, Packages, Copilot and Git operations after an automated infrastructure process changed runtime config and broke service discovery. A...
This one annoyed me, in the good way. Researchers took 206 real developer-agent sessions from 13 developers, extracted each developer's preferences from their actual interaction traces via rule-based bootstrapping plus evidence-grounded refinement, then replayed everything aga...
An open-weight Chinese frontier model is now a dropdown option in Microsoft's coding product. That happened before anyone finished characterizing what the model does. GitHub's changelog dated August 6 makes Kimi K3 generally available across Copilot Pro, Pro+, Max, Business an...
The sunset notice is short and it doesn't hedge. Code freeze July 29. Repository archived August 10. Core team gone August 31. npm and Docker packages deprecated. Flowise has 55,186 stars and 24,850 forks under Apache-2.0, and the team wrote its own cause of death: developers...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.