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

release/provenance/npm

Releases attest build provenance

Implements release/provenance for the npm artifact: it runs when the release publishes one (see artifacts).

Severitywarning
Tiers1
Artifactnpm
Scoperoot
Kindoutcome
Sourcelibrary v0.4.0
Selected byfleetlint-recommended@v0.4.0

Requirement

The package is published to npm with provenance (--provenance, NPM_CONFIG_PROVENANCE, or trusted publishing with id-token: write); the registry’s provenance is the 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 || repo.artifacts.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 files (or subject-name and subject-digest for an image, with push-to-registry: true); 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.

Sources


Generated by fleetlint docs from catalog v0.4.0.