Review code and releases
Follow a change from the commit that was signed to the job and account that publish it. Use a test repository or package so you can see which permissions each step actually uses.
Choose a setup guide
- Verify a signed change on GitHubApprove a test commit on your phone, then check that GitHub marks the same commit as verified.
- 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.
- Rehearse publishing to PyPI from GitLabRehearse a test release from a GitLab.com project and verify that TestPyPI trusts the intended pipeline.
- Check who can merge a code changeFind the review decision for a specific revision and check what allows it to land in Bitbucket Cloud, Azure Repos, Gerrit or SourceHut.
- Test an approval gate before a releaseCheck which account can approve a test release and whether that approval lets the next job run in CircleCI, Buildkite, Jenkins or GitLab CI/CD.
- Check a trusted publisher on crates.io or NuGetTrace an existing package version back to its publishing workflow. These examples use GitHub Actions and the registry's trusted publishing settings.
- Check what signs a Linux package or repositorySee which public key your package manager trusts for one source or package in Ubuntu, Debian or Red Hat Enterprise Linux.
- Verify a detached file signatureCheck which key signed a sample file, then change one byte and confirm the same signature fails.
- Verify who signed a container imagePin a test image by digest and require the intended publisher before a build or deployment accepts it.
- Check an approved container image with NotationVerify the publisher with Notation and check that the same container image digest is the one your KeySigner release owners approved.
- Check an approved Docker Hub image digestCheck that Docker Hub serves the exact multi-platform image your KeySigner release owners approved. Practice with the public hello-world image without publishing or changing a tag.
- Troubleshoot a package release approvalIf your GitHub Actions workflow already waits for KeySigner approval before publishing to npm, use the request ID to see where the release stopped and what you can safely retry.
- 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.
- Check an approved package with CosignUse KeySigner to check the package archive your release owners approved. Use Cosign to verify which publisher signed those same bytes.
- Check an approved npm archive with OpenSSL or GnuPGCheck who signed an npm archive and whether it matches the exact bytes your release owners approved in KeySigner.
- Verify a signed RPM against a KeySigner approvalCheck that a signed RPM came from the expected publisher and matches the exact package your release owners approved in KeySigner.
Check your result
Check the identity shown on the signed change and the separate permissions required to merge or publish. Where you test a release, confirm what the registry received.