release/signing/node
Release artifacts are signed
Implements release/signing for node.
| Severity | error |
| Tiers | 1 |
| Stacks | node |
| Scope | root |
| Kind | outcome |
| Source | library v0.2.0 |
| Selected by | fleetlint-recommended@v0.2.0 |
Requirement
Packages are published to npm with provenance (npm publish --provenance, NPM_CONFIG_PROVENANCE, or trusted publishing with id-token: write), which npm signs with Sigstore; or a stack-neutral signature: cosign, GoReleaser, gpg.
Why
Checksums prove integrity; only a signature proves who built it.
Capability applies when
release.exists && tagged_workflows().size() > 0Fix
Publish with npm publish --provenance from a job with id-token: write, or use trusted publishing.
Agent instruction: Use the stack’s signing format when the stack 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.
See: https://fleetlint.org/baseline/#releases, https://fleetlint.org/stacks/#nodejs--typescript, https://docs.npmjs.com/generating-provenance-statements
Generated by fleetlint docs from catalog v0.2.0.