GitHub partners with code-signing service Sigstore to add support for signing npm software packages, helping improve the security of open source projects
most people just don't believe you or are terrified.” Dramatic supply chain updates from @lorenc_dan @jhutchings0 @npmjs @projectsigstore https://www.wired.com/... @npmjs : Today we opened an RFC with a proposal of how npm can collaborate with @projectsigstore to link packages to their source and build, a significant improvement to the supply chain security of the JavaScript ecosystem. https://github.blog/... @mylesborins : Extremely excited about this. The npm team has been collaborating with GitHub's package security team for months putting together an RFC to improve the audibility and trust of npm packages using SigStore and trusted build infrastructure https://github.blog/... Dan Lorenc / @lorenc_dan : HUGE NEWS for @npmjs and @projectsigstore! https://github.blog/... Abhishek Arya / @infernosec : Yet another win for @projectsigstore. NPM published a RFC to add support for end-to-end signing of npm packages. This joins in the growing list of ecosystems that have expressed interest - Python, RubyGems and Maven - https://github.blog/...
Context & Ripple Effects
GitHub has been tightening npm's defenses in stages since it acquired the registry in 2020: first patching flaws that let attackers bypass authentication and publish any package, then enrolling top maintainers into mandatory two-factor authentication. The Sigstore partnership is the next layer — an RFC proposing that every npm package be linked to its source and build through end-to-end signing.
First-order effects
- npm publishers gain a signing workflow built into their existing GitHub tooling, while package consumers can verify that a downloaded artifact matches its claimed source rather than trusting the registry's word.
Second-order effects
- Attackers relying on unsigned-package vectors — the class of dependency confusion attacks that hit Microsoft, Zillow, and Lyft — face a higher bar once provenance is checkable by default, pressuring other package ecosystems to answer with equivalent signing schemes.
Third-order effects
- Because GitHub owns both the registry and the developer platform where code is written, reviewed, and built, it can make signed provenance a default rather than an opt-in — setting the de facto trust standard for the JavaScript ecosystem and normalizing Sigstore, the Linux Foundation initiative backed by Google and Red Hat, as shared infrastructure across projects.
The trend: Open source package distribution is shifting from reputation-based trust to cryptographically verified provenance, with platform owners like GitHub deciding how fast that default arrives.