10 Billion Devices Run His Code — And He Maintains It Alone
🌍 10 Billion Devices Run His Code — And He Maintains It Alone
Category: Open Source / Infrastructure
Source: Can Artuc (Feb 17, 2026)
-
Daniel Stenberg has maintained curl since 1996, expanding it from the original “httpget” into one of the most widely deployed internet transfer tools in history.
-
Today, curl ships with Windows, macOS, Linux, Android, iOS, and all major gaming consoles. It is embedded in an estimated 10 billion installations worldwide — yet only ~10 developers contribute regularly.
Key Insight: A foundational internet dependency has a bus factor of one.
🚗 47 Car Brands Ship curl — None Employ Its Maintainer
Category: Software Supply Chain / Sustainability
-
According to project documentation, 47 distinct car manufacturers ship curl in their vehicles.
-
Major tech companies — including Apple, Microsoft, Google, and Amazon — distribute curl in their platforms, but none employ Stenberg directly.
He works at wolfSSL, which sponsors his maintenance time — a small company effectively supporting infrastructure used by trillion-dollar corporations.
Systemic Gap: Massive corporate adoption does not translate into proportional financial or engineering support.
🤖 AI-Generated Bug Reports Are Flooding the Project
Category: AI / Developer Tooling Risk
-
Beginning in late 2024 and escalating through 2025, Stenberg documented a surge of AI-generated fake vulnerability reports.
-
Individuals prompt tools like ChatGPT or Claude to “find vulnerabilities in curl,” then submit hallucinated issues — sometimes requesting CVEs.
Each fabricated report requires manual verification because a real vulnerability could impact billions of devices.
Stenberg described the phenomenon as a “DDoS attack on maintainers.”
The project now requires contributors to confirm reports are not AI-generated and has begun banning repeat offenders.
Developer Impact: AI reduces friction for spam generation, but the validation burden remains human.
🏆 Developer of the Year — While Writing About Burnout
Category: Maintainer Health / Industry Recognition
-
In 2025, Sweden named Daniel Stenberg Developer of the Year.
-
During the same period, he published blog posts about burnout and sustainability challenges.
The contrast highlights a structural issue: recognition without long-term support does not solve maintainer overload.
🚌 The Bus Factor Problem
Category: Supply Chain Risk
-
curl’s bus factor is effectively one.
-
After nearly 28 years of accumulated protocol complexity, replacing Stenberg would require years of knowledge transfer.
The article compares this to the 2014 OpenSSL Heartbleed incident, where critical infrastructure maintained by a tiny team exposed systemic industry underinvestment.
Risk Framing: Maintainer sustainability is a security issue, not just a staffing issue.
🔄 Three Structural Changes Proposed
1. Sustained Corporate Funding
Companies shipping curl should employ maintainers or fund contracts — similar to how companies fund Linux kernel development.
2. Platform-Level AI Spam Controls
Issue tracker platforms should detect AI-generated vulnerability spam automatically, instead of relying on maintainers to filter it.
3. Supply Chain Sustainability Audits
Software audits should include maintainer bus factor and funding stability as risk metrics.
🧠 Developer Takeaway
curl is not a side project. It is invisible internet infrastructure.
If your systems depend on it — and they almost certainly do — sustainability is your problem too.
Critical dependencies maintained by a single individual represent operational, security, and continuity risk.
Comments
Post a Comment