Open Source Fails When Nobody Funds the Maintainers
Since 11 September 2026, the Cyber Resilience Act gives manufacturers 24 hours to report actively exploited vulnerabilities, including in components nobody maintains anymore. 93% of codebases contain such a component.
contain open source components with no development activity in over two years (Black Duck OSSRA 2026)
The number
Black Duck’s 2026 Open Source Security and Risk Analysis, published in March 2026, is based on 947 commercial codebases audited between November 2024 and October 2025. Its findings:
- 98% of codebases contain open source, with 1,180 components on average, up 30% in one year.
- 64% of those components are transitive dependencies that nobody chose explicitly.
- 93% of codebases contain components with no development activity in over two years.
- Only 7% of components run their latest version.
Open source is universal. Maintenance is not.
Since September, it is a compliance problem
The EU Cyber Resilience Act has applied its vulnerability reporting duties since 11 September 2026. Manufacturers must report actively exploited vulnerabilities to their national CSIRT and to ENISA: an early warning within 24 hours, a notification within 72 hours, and a final report within 14 days after a fix is available. All other obligations follow on 11 December 2027.
The duty also flows upstream: a manufacturer that learns of a vulnerability in a component has to report it to whoever maintains that component.
For a zombie component, nobody does. Then there are three options, and none is cheap: fork it and maintain it yourself, replace it and refactor, or accept the risk.
The maintainer is the supply chain
Unmaintained code is one risk. Overstretched maintainers are another. Of the malicious packages Black Duck identified, 34% were hijacked legitimate packages, often through maintainer account takeover. The second wave of the Shai-Hulud worm in November 2025 compromised nearly 800 npm packages and leaked more than 400,000 credentials.
An unpaid maintainer with no time for security hygiene is not a community problem. It is an entry point into your product.
Who is paying today
Germany’s Sovereign Tech Fund had invested €33.6 million in 96 technologies by late 2025. On 3 June 2026, the European Commission adopted its EU Open Source Strategy as part of the Technological Sovereignty Package. One of its three pillars is explicitly about who sustains open source, not only who uses it.
The CRA also creates the role of the open source steward. Foundations such as Apache, Eclipse and the Linux Foundation are expected to take it on. Stewards need a cybersecurity policy and must cooperate on vulnerabilities, but they do not face manufacturer penalties.
Public money will not cover your dependencies. The companies shipping the products will have to.
What an OSPO should do this quarter
- Inventory with depth. An SBOM that covers transitive dependencies, not only the direct ones the CRA requires.
- Flag the zombies. Every critical component without a commit or release in 24 months.
- Decide before the next CVE. For each critical zombie: fund it, maintain a fork, or replace it.
- Budget upstream time. Paid maintainer hours on the components your products depend on.
- Prefer stewarded components. A foundation or a named steward on the critical path, as argued in Open Source Risk Is Governance, Not License.
Track the share of critical components with an active maintainer, the median component age (45 months in OSSRA 2026), and the time from disclosure to fix.
The bill
Open source is free to use. It was never free to maintain. Since September, the cost of nobody maintaining it arrives with a 24-hour deadline.
Sources
- Black Duck, 2026 Open Source Security and Risk Analysis, Mar 2026
- Sovereign Tech Agency, Newsletter November 2025
- European Commission, Commission boosts open and interoperable digital ecosystems, Jun 2026, and EU Open Source Strategy