Securing Packages in npm, Homebrew, PyPI, Maven Central, and...
summary
Package registries move from brittle GPG signatures to Sigstore attestations that embed nonfalsifiable links to source commit, build instructions, and build logs, signed via OIDC tokens and uploaded to a public transparency log; builders create ephemeral signing keys then discard private keys so signatures are single use. This pipeline helps detect and respond to incidents like the December 2024 Ultralytics PyPI compromise by showing exact malicious commits and build logs. npm adopted in 2023, Homebrew/PyPI/RubyGems in 2024, Maven Central this year.
AI-written summary · about
chapters (7)
- 0:00Package repository security intro
- 3:46Software supply chain security
- 7:59Build provenance with OIDC
- 11:50Adoption for maintainers
- 13:59Real-world attack response
- 16:08Ecosystem adoption plans
- 18:40Q&A
related talks
39mnpm and Sigstore: Provenance Comes to the World's Largest OSS Ecosystem
23mSecuring the npm Ecosystem
27mBringing Provenance to All of Open Source: Lessons from Npm’s Sigstore Integration
36mWhere Does Your Software (Really) Come from?
36mSigstore: Past, Present and Future Directions
23mBuilding Secure Package Pipelines
39m"Malice in the Modules" - How NPM Became a Supply-Chain Battleground?
30mSecuring Open Source Supply Chains