Open Infrastructure is Not Free: A Joint Statement on Sustainable Stewardship
automated CI systems, large-scale dependency scanners, and ephemeral container builds" all downloading enormous amounts of package data, coupled with the rise of generative and agentic AI "
driving a further explosion of machine-driven, often wasteful automated usage, compounding the existing challenges". It is not a crisis, yet, they say, but it is headed in that direction.
Despite serving billions (perhaps even trillions) of downloads each month (largely driven by commercial-scale consumption), many of these services are funded by a small group of benefactors. Sometimes they are supported by commercial vendors, such as Sonatype (Maven Central), GitHub (npm) or Microsoft (NuGet). At other times, they are supported by nonprofit foundations that rely on grants, donations, and sponsorships to cover their maintenance, operation, and staffing.Regardless of the operating model, the pattern remains the same: a small number of organizations absorb the majority of infrastructure costs, while the overwhelming majority of large-scale users, including commercial entities that generate demand and extract economic value, consume these services without contributing to their sustainability.
Posted Sep 23, 2025 15:49 UTC (Tue)
by Kamiccolo (subscriber, #95159)
[Link] (1 responses)
Posted Sep 23, 2025 15:54 UTC (Tue)
by jake (editor, #205)
[Link]
thanks,
jake
Posted Sep 23, 2025 16:05 UTC (Tue)
by cen (subscriber, #170575)
[Link] (6 responses)
Posted Sep 23, 2025 17:07 UTC (Tue)
by yodermk (subscriber, #3803)
[Link] (5 responses)
Posted Sep 23, 2025 19:23 UTC (Tue)
by ibukanov (subscriber, #3942)
[Link]
I also wish language runtimes would demand populated local caches instead of automatically downloading things by default so at least not using local cache would take more efforts than not.
Posted Sep 23, 2025 19:31 UTC (Tue)
by fraetor (subscriber, #161147)
[Link] (2 responses)
I guess you would probably want a signed and timestamped index that contains package hashes that is only valid for a few hours, to avoid being vulnerable to getting served an old version of a package. Or perhaps I'm overcomplicating it, and the metadata should always query the source repository, and only the package data should be mirrored.
If we can trust it to be secure, then perhaps CI systems could inject an environment variable with an alternative repository URL to use, transparent to users of the CI system.
Posted Sep 23, 2025 20:02 UTC (Tue)
by NAR (subscriber, #1313)
[Link] (1 responses)
I think for build reproducibility (and to avoid breaking changes) some environments do prefer to download the same (old) version and not the latest and greatest.
Posted Sep 23, 2025 21:07 UTC (Tue)
by fraetor (subscriber, #161147)
[Link]
I'm more talking about when you request the latest version of a well known package, an attacker may want to make the "latest" version appear to be an old one, so they can take advantage of security issues that have since been fixed, and would be able to provide a valid signature because that package _was_ legitimately served by the repository, just before the vulnerability was fixed.
Posted Sep 23, 2025 21:10 UTC (Tue)
by ballombe (subscriber, #9523)
[Link]
Missing a link?
https://openssf.org/blog/2025/09/23/open-infrastructure-i...
Missing a link?
simple
simple
simple
Mirror security
to avoid being vulnerable to getting served an old version of a package
Mirror security
Mirror security
simple
It seems like developers now have lost all their sysadmin skill.