Open Source Myths vs. Facts: What the Headlines Get Wrong About Maintenance

Archi3 min read

open-sourcesecuritysoftwaremaintenance

Contents
  1. The headlines keep saying open source is broken
  2. Myth: Most open source projects are abandoned
  3. Myth: Volunteers alone hold up the internet
  4. Myth: Open source is less secure than proprietary software
  5. Myth: Maintainer burnout is a new problem
  6. Myth: The fix is more money
  7. What the headlines should ask next

The headlines keep saying open source is broken#

Another critical vulnerability in a widely used library. Another maintainer stepping away. Another post about the "tragedy of the commons" in software. The stories follow a pattern: open source is fragile, underfunded, and held together by volunteers who burn out. There is truth in parts of that. But the headlines consistently miss what the data shows about how open source actually works, who fixes it, and why some projects survive while others do not.

Myth: Most open source projects are abandoned#

Fact: Most open source projects are small and were never meant to be long-term products. The numbers look alarming because registries count everything. A package that one developer published in 2014 to solve a single problem and never touched again is technically "abandoned." It is also not a crisis.

The projects that matter, the ones with millions of downloads and dependencies across thousands of applications, tell a different story. Research from software supply chain firms has found that a small share of maintainers produces most of the code that other projects rely on. When a critical library needs a security patch, the response time is often measured in hours, not months. The problem is not that nobody is home. It is that too few people are home, and the headlines rarely distinguish between the two.

Myth: Volunteers alone hold up the internet#

Fact: Corporate funding of open source has grown, but unevenly. Companies that depend on a project often pay maintainers, either directly through sponsorship or by employing them. The catch is that this support clusters around projects that are already visible. A logging library used by every cloud provider gets attention. A date parsing utility used by a single industry does not.

The headline gap: when a project fails, the story focuses on the lone maintainer. It rarely asks which companies used the software without contributing, or why their security teams did not notice a dependency that had been unmaintained for years. The failure is real. The framing is incomplete.

Myth: Open source is less secure than proprietary software#

Fact: The evidence is mixed, and the comparison is often apples to oranges. Proprietary software can hide vulnerabilities behind closed code, which means fewer people can find them but also fewer people can check. Open source exposes code to anyone who wants to look, but looking is not the same as auditing.

The real difference is process. A project with a security policy, a disclosure channel, and a patching routine tends to handle vulnerabilities better than one without, regardless of license. The headlines that treat "open source" as a single security category miss this. A well-run open source project can be more responsive than a commercial vendor that takes six weeks to issue a patch. A poorly run project can be worse than either.

Myth: Maintainer burnout is a new problem#

Fact: Burnout has been documented in open source for more than a decade. What changed is visibility. When a maintainer of a widely used package announced they were stepping back, the story went viral. Similar departures happened years earlier without notice.

The overlooked detail: burnout is often triggered by the same pattern. A project becomes popular, users demand support, and the maintainer has no way to say no without being called unresponsive. Funding helps, but it does not solve the boundary problem. Some projects have adopted formal governance and paid maintainer roles. Others have not. The headlines rarely explain which model a project uses until after something breaks.

Myth: The fix is more money#

Fact: Money helps, but it is not the only lever. A project with one paid maintainer and no documentation is still fragile. A project with clear contribution guidelines and a rotating release team can survive turnover.

The more useful question is what kind of support a project needs. Some need full-time maintainers. Some need security audits. Some need better documentation so that users stop filing the same issues. Treating every project as underfunded misses the ones that are adequately funded but poorly structured.

What the headlines should ask next#

When the next open source failure makes news, the useful questions are specific. Which versions are affected? Who maintains the project, and how are they funded? What does the security policy say? Did the organizations that depend on it know they were exposed?

Those questions do not fit a headline. They do explain why some projects recover quickly and others do not. The difference is rarely whether the code is open. It is whether anyone built a process around it.

More articles