fleetlint Policy for a fleet of repositories
v0.5
Getting started

release/provenance/node

Releases attest build provenance

Implements release/provenance for node.

Severitywarning
Tiers1
Stacksnode
Scoperoot
Kindoutcome
Sourcelibrary v0.2.0
Selected byfleetlint-recommended@v0.2.0

Requirement

Packages are published to npm with provenance (--provenance, NPM_CONFIG_PROVENANCE, or trusted publishing with id-token: write); or a stack-neutral attestation.

Why

Provenance ties the artifact to the exact source and workflow that built it, which a signature alone does not.

Capability applies when

release.exists && tagged_workflows().size() > 0

Fix

Publish with npm publish --provenance from a job with id-token: write, or use trusted publishing.

Agent instruction: Add a step uses: actions/attest-build-provenance with subject-path covering the release artifacts; grant id-token: write and attestations: write to that job only. On GitLab set the variable RUNNER_GENERATE_ARTIFACTS_METADATA to “true” on the release job. On Gitea write a SLSA v1 predicate and run cosign attest-blob --type slsaprovenance1.

See: https://fleetlint.org/baseline/#releases, https://slsa.dev/spec/v1.0/provenance, https://fleetlint.org/stacks/#nodejs--typescript, https://docs.npmjs.com/generating-provenance-statements


Generated by fleetlint docs from catalog v0.2.0.