agent-release.yml workflow in jiordiviera/webhooktrap from a tag agent-v<version>. The builds are reproducible. Each release has:
Each archive also has a SLSA build provenance attestation on GitHub, and the npm packages are published with npm provenance.
With the install script
install.sh does the checks below for you. Make the signature check mandatory:
PATH, the script still checks the SHA-256, says that the signature was not checked, and prints the commands to check it yourself.
By hand
This example verifies releaseagent-v1.0.0 for Linux on amd64. Change the archive name for your platform.
1
Download the archive, the checksums and the signature bundle
2
Verify the signature of SHA256SUMS with cosign
The certificate identity must be the release workflow at that tag, issued through GitHub Actions:Install cosign from docs.sigstore.dev.
3
Check the archive against SHA256SUMS
shasum -a 256 --ignore-missing -c SHA256SUMS.4
Check the build provenance (optional)
SHA256SUMS.pem shows who signed (openssl x509 -in SHA256SUMS.pem -noout -text; the subject alternative name must be the workflow URL above). Checking SHA256SUMS.sig against it with openssl skips the Sigstore certificate chain and transparency log, so it doesn’t replace cosign or gh attestation verify.npm installs
In a project that depends on@webhooktrap/agent, check the registry signatures and provenance attestations: