What to check first
Get the expected publisher fingerprint from a trusted source and verify the detached signature on the exact archive.
KeySigner setups
- Verify the OpenPGP signer and compare the archive with the release approval →KeySigner release history and GnuPG with --assert-signer
KeySigner setup requirements →
Provider walkthroughs
What it covers
The release check covers the archive digest. OpenPGP key trust, encryption and recovery are separate.
Troubleshooting
Does a signature verify under a key you did not expect?
Compare the full fingerprint with your release policy and verify the detached signature with that fingerprint. Compute SHA-256 on the verified archive and compare it with the KeySigner release approval.
Check an approved npm archive with OpenSSL or GnuPG →
Check whether GnuPG can see the intended key on this device. If the operation also fetches a key, check the configured keyserver separately.
Documentation and support
GnuPG documentation
Verify signatures and signing key fingerprints
Check GnuPG’s signer fingerprint option