In a joint statement backed by the Open Source Security Foundation (OpenSSF), major technology leaders including Arm, Datadog, Dell Technologies, Ericsson, GitHub, Google, IBM, Kusari, Microsoft,
Red Hat, Rust Foundation, and Sonatype
have recognized that the current funding model for public package registries is no longer sustainable. As rapid artificial intelligence adoption reshapes software development and dramatically increases demand on infrastructure, these enterprise consumers are stepping forward with a public commitment to participate as paying commercial customers.
Public package registries such as PyPI, Maven Central, crates.io, RubyGems, npm, NuGet, OpenVSX, and Packagist serve as the foundation of the global software supply chain. Nearly every software application built today relies heavily on these distribution hubs, which collectively process trillions of package downloads every year. However, despite their vital role in modern technology, most package registries continue to operate on fragile financial footing—surviving largely on donated infrastructure credits and the efforts of small operational teams.
The Growing Crisis: AI Acceleration and Security Threats
The urgency behind this industry initiative stems from compounding technical and operational pressures, the group said. Annual download volumes across package registries are growing by 30% to 50% year over year, a trend accelerated significantly by the explosion of autonomous AI coding agents. At the same time, the security landscape has become increasingly hostile.
Security researchers have identified over 1.8 million malicious packages in 2026 alone—already surpassing the total volume recorded in 2025. Furthermore, with the influx of automated, AI-discovered vulnerabilities, registries anticipate a 3x to 5x surge in package publish events alongside severe support and analysis burdens. Small teams of two or three maintainers can no longer absorb these demands without adequate, recurring financial resources, the OpenSSF said in the announcement.
Sustainable enterprise funding seeks to evolve registries from survival mode into enterprise-ready infrastructure. With predictable revenue, registries can deliver:
- Enhanced Availability & Performance: High-reliability publication, dedicated support, private access options, and distribution optimizations to prevent downtime.
- Ecosystem Observability & Compliance: Comprehensive analytics, publish/consumption auditing, and advanced compliance tracking for enterprise software supply chains.
- Proactive Security Protections: Funded implementation of artifact signing, trusted publishing workflows, automated malware quarantine, build provenance attestations, and SBOM/VEX generation.
Crucially, the signatories emphasize that open source will remain free for individual developers, hobbyists, and small organizations, ensuring no barriers are introduced to community innovation.
The Role of the Sustaining Package Registries Working Group
Hosted by the Linux Foundation, the Sustaining Package Registries Working Group serves as the central collaborative forum for cross-registry governance and strategy. Achieving long-term infrastructure health requires industry-wide coordination rather than isolated efforts, the group said.
The working group brings together registry stewards, maintainers, and enterprise consumers to:
- Share Best Practices: Exchange operational, security, and technical blueprints across different language ecosystems.
- Explore Sustainable Business Models: Pilot and refine enterprise usage tiers, mirrored distribution frameworks, and commercial service agreements tailored to scale.
- Preserve Registry Autonomy: Ensure that each registry retains full independence over its governance, architecture, and pricing structures without external dictation.
By uniting enterprise consumers around shared commitments, the Sustaining Package Registries Working Group seeks sustainable paid enterprise participation, providing package registries with the long-term support needed to protect the open source ecosystem.
SD Times Q&A
Why are public package registries like PyPI and npm running out of funding?
Most public package registries operate on donated infrastructure credits and small volunteer teams rather than sustainable commercial revenue. Annual download volumes are growing 30–50% year over year, driven partly by AI coding agents, while security threats such as malicious packages are increasing sharply. This mismatch between demand and resources has pushed registries into financial instability.
What is the Sustaining Package Registries Working Group and who runs it?
The Sustaining Package Registries Working Group is a Linux Foundation-hosted initiative that brings together registry stewards, maintainers, and enterprise consumers to coordinate cross-registry governance and strategy. It was backed by a joint statement from the OpenSSF and major technology companies including Google, Microsoft, GitHub, IBM, Red Hat, and others. Its goal is to pilot sustainable business models such as enterprise usage tiers and commercial service agreements.
Will enterprise funding for package registries make open source packages cost money for individual developers?
According to the signatories of the joint OpenSSF statement, open source packages will remain free for individual developers, hobbyists, and small organizations. The proposed model targets enterprise commercial customers, not the broader developer community. The intent is to preserve open access while creating a sustainable revenue layer for large-scale consumers.
How are AI coding agents affecting package registry infrastructure?
AI coding agents are significantly accelerating download volumes across package registries, contributing to annual growth rates of 30–50%. The group also anticipates a 3x–5x surge in package publish events driven by automated, AI-discovered vulnerabilities and agent-generated code. This creates compounding pressure on both infrastructure capacity and the small security teams that vet packages.
What security capabilities would enterprise funding enable for package registries?
With predictable enterprise revenue, registries could implement artifact signing, trusted publishing workflows, automated malware quarantine, build provenance attestations, and SBOM/VEX generation. These capabilities address the growing volume of malicious packages—over 1.8 million identified in 2026 alone according to the OpenSSF announcement. Currently, small operational teams cannot fund or staff these protections adequately.
