release/signing/npm
Release artifacts are signed
Implements release/signing for the npm artifact: it runs when the release publishes one (see artifacts).
| Severity | error |
| Tiers | 1 |
| Artifact | npm |
| Scope | root |
| Kind | outcome |
| Source | library v0.4.0 |
| Selected by | fleetlint-recommended@v0.4.0 |
Requirement
The package is published with provenance (npm publish --provenance, NPM_CONFIG_PROVENANCE, or trusted publishing with id-token: write), which npm signs with Sigstore; that signature is what npm audit signatures checks.
Why
Checksums prove integrity; only a signature proves who built it.
Capability applies when
release.exists || repo.artifacts.size() > 0Fix
Publish with npm publish --provenance from a job with id-token: write, or use trusted publishing.
Agent instruction: Use the artifact’s own signing format when it has one. Otherwise add sigstore/cosign-installer and a signing step after the artifacts are built. Files: cosign sign-blob --yes --bundle checksums.txt.sigstore.json checksums.txt and upload the bundle. Container image: cosign sign --yes <image>@<digest> using the digest output of the build step, with id-token: write on the job.
Sources
- https://csrc.nist.gov/pubs/sp/800/218/final (standard, PS.2.1: Make software integrity verification information available to software acquirers)
- https://github.com/ossf/scorecard/blob/main/docs/checks.md (standard, Signed-Releases)
- https://fleetlint.org/baseline/#releases
- https://docs.npmjs.com/generating-provenance-statements (spec)
Generated by fleetlint docs from catalog v0.4.0.