Consider Adopting NPM Trusted Publishing

[Cevan00]

Overview

Recent supply chain attacks on npm have highlighted the need for stronger package publishing security. The September 2025 Shai-Hulud worm compromised 500+ packages through stolen maintainer tokens, showing the risks of token-based publishing.

Trusted publishing helps by eliminating long-lived tokens that can be stolen or accidentally exposed; generating automatic provenance provides cryptographic proof of where/how packages are built; and is an industry standard adopted by PyPI, RubyGems, crates.io, NuGet, etc...

NPM is planning to deprecate legacy tokens and make trusted publishing the preferred method.

If assistance is welcome, please let me know and I can assist and/or get further assistance as needed.

Reference

References:

• NPM trusted publishing documentation
• Announcement blog post
• Provenance statements guide

[Subham-KRLX]

Sir i would like to work on this issue can you please assign to me.

[manu-bitt]

Hi, I’d like to help with adopting NPM Trusted Publishing. Could you please confirm if this is open for contribution?

[Cevan00]

Yes, as long as it gets implemented 🙂