npm + KeySigner

Protect maintainers of a package and review how new versions get published.

What to check first

Check package owners, publishing policy and how trusted automation publishes. Rehearse with a throwaway package.

KeySigner setups

KeySigner setup requirements →

Provider availability

Trusted publishing from GitHub Actions. Requires a GitHub-hosted runner for this workflow. Check provider requirements →

Provider walkthroughs

What it covers

Account protection does not revoke a publisher or job that already has release permissions.

Make an offline recovery plan →

Troubleshooting

Does a publishing workflow fail to prove its identity?

Compare the trusted publisher saved for the package with the exact CI identity of the failing run. For GitHub Actions, check the repository, workflow filename and environment. If the job still uses a classic token, npm revoked those tokens on December 9, 2025.

Replace retired credentials for Bitbucket, npm, and PyPI →

Check npm status for reports on the npm registry and website.

Find documentation and support →

Documentation and support

npm documentation

Review trusted publishers

KeySigner setup help

Ask about this setup →