What to check first
Check package owners, publishing policy and how trusted automation publishes. Rehearse with a throwaway package.
KeySigner setups
- Compare approved and published package bytes →KeySigner console and access to the npm test package
- Check an approved package with Cosign →KeySigner release history and Cosign
- Check an approved npm archive with OpenSSL or GnuPG →KeySigner release history and OpenSSL
KeySigner setup requirements →
Provider availability
Trusted publishing from GitHub Actions. Requires a GitHub-hosted runner for this workflow. Check provider requirements →
Provider walkthroughs
- Review the path from GitHub Actions to npmSeparate the person who approves a release from the workflow that publishes it. Rehearse the handoff before changing a real package.
- Replace retired credentials for Bitbucket, npm, and PyPIFind out which credentials stopped working, what replaces them, and how to check repository access or package publishing before changing a live workflow.
What it covers
Account protection does not revoke a publisher or job that already has release permissions.
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.