Open Source vs the Invisible Hand
The article shows how open source software breaks every textbook market rule—non-excludable, free to use, mostly single‐maintainer—and yet it thrives at massive scale. It walks through classic market failures and existing theories, argues none fully explain open source’s resilience, and critiques efforts to retrofit pricing signals onto a system built on gifts, reputation, and shared infrastructure.
- npm hosts 5M+ packages, mostly unfunded and maintained by lone contributors, with no grants or contracts backing them—yet the entire commercial software world depends on them.
- Classic market failures (free riding, tragedy of the commons) just don't manifest: downloads can jump from 1,000 to 10 million weekly without any increase in maintainer headcount, and over half of packages survive on a single maintainer.
- Existing economic theories (Lerner/Tirole's reputation signaling, Benkler's coordination costs, Von Hippel's user innovation) each explain fragments but fail to account for why maintainers keep triaging bugs on abandoned tools or why the ecosystem hasn't collapsed in three decades.
- Proposed fixes—bug bounties, sponsorship marketplaces, token rewards—all try to impose pricing onto a giftand-reputation system, relying on weak proxies like stars and download counts instead of answering who's actually sustaining the code.
Open source libraries routinely flout every core market assumption. They’re non-rival and non-excludable, yet npm hosts over five million of them—almost none funded by grants. A single `npm install` call can pull in hundreds of packages maintained largely by lone contributors whose day jobs lie elsewhere. Users don’t pay, sign contracts or face liability, yet the commercial software world runs on these “impossible goods.”
Traditional problems—free riding, missing price signals, tragedy of the commons—simply don’t appear at scale. SQLite, one of the world’s most deployed database engines, sits next to typosquats and crypto-miner traps at the same zero price. Demand can jump from 1,000 to 10 million weekly downloads without raising maintenance headcount. Over half of public packages have just one maintainer. Even titans like Google, Meta and Microsoft pump resources into each other’s projects without any clear market return.
Economists have chipped away at the puzzle. Lerner and Tirole point to reputation signaling, Benkler to coordination costs falling, Von Hippel to user innovation. Each explains a slice—career boosts, easier group work, building tools you need—but none account for long-term bug-report triage on abandoned tools, or why the whole ecosystem hasn’t collapsed over three decades.
All proposed “fixes” assume a market context. Bug bounties, sponsorship marketplaces, dependents-weighted funding and token rewards all try to slap a price on code that’s never carried one. They lean on weak proxies—download counts, GitHub stars, criticality scores—because the real questions remain: who’s actually keeping this running, how close are they to giving up, and will someone respond when a security flaw turns up?