Survey of ~400 open-source code maintainers reveals poor pay, with 46% saying they go unpaid and, of those who were paid, only 26% say they earn $1K+ annually
Maintaining open-source code is a vital but stressful job. Despite that, a recent Tidelift survey found that almost half of code maintainers aren't paid at all. Tweets: @aschmitt Tweets: Andrew Schmitt / @aschmitt : File this under “things that should not be a surprise” https://twitter.com/...
Context & Ripple Effects
Tidelift's survey lands mid-arc on an old problem: two years earlier, research on Open Collective funding found that more than 80% of the most popular funded open-source projects still earned below industry standards or the poverty line, and the OpenSSL economics debate had already framed unpaid maintenance as a security risk, not just a labor issue.
The company behind the survey is not a neutral observer — it sells subscriptions meant to fund maintainers' patching work, so the data doubles as market sizing for its own model. Six months later, the Log4Shell response would make the stakes explicit when the zero-day fixer described working on Log4j in his spare time.
First-order effects
- Tidelift gets quantitative ammunition for its pitch: with 46% of ~400 surveyed maintainers unpaid and only 26% of paid ones earning $1K+, the subscription-for-maintenance market has both a supply problem and a sales argument.
- Downstream enterprises that depend on this code now have survey-grade evidence that critical dependencies rest on uncompensated volunteers.
Second-order effects
- Rival funding mechanisms — donation platforms like Open Collective, foundation stipends, corporate sponsorships — face pressure to convert goodwill into reliable income streams, since the survey shows sporadic payment fails to reach most maintainers.
- Buyers of enterprise software gain leverage to demand that vendors fund the upstream components they ship, shifting maintenance cost negotiations into procurement.
Third-order effects
- If the pattern holds, open-source sustainability moves from charity to infrastructure policy: the professionalization debate around spare-time maintainers points toward paid stewardship as standard practice for widely deployed code, much as roads and utilities are funded.
- Uncompensated maintenance becomes a recognized systemic risk category for regulators and insurers assessing software supply chains, alongside the burnout and abandonment already documented since the OpenSSL era.
The trend: Open-source maintenance is being pushed from volunteer labor toward compensated infrastructure roles, with surveys like Tidelift's converting burnout anecdotes into fundable market evidence.