release/provenance/crate
Releases attest build provenance
Implements release/provenance for the crate artifact: it runs when the release publishes one (see artifacts).
| Severity | warning |
| Tiers | 1 |
| Artifact | crate |
| Scope | root |
| Kind | expr |
| Source | library v0.7.0 |
| Selected by | fleetlint-recommended@v0.7.0 |
Requirement
crates.io has no provenance attestations yet; a crate is checked for trusted publishing (release/trusted-publishing/crate).
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() > 0Applies when
falseCheck
trueFix
Add actions/attest-build-provenance (GitHub), RUNNER_GENERATE_ARTIFACTS_METADATA: "true" (GitLab) or cosign attest-blob --predicate (Gitea) to the release pipeline for files, cosign attest or BuildKit provenance for an image; a package published to npm, PyPI or RubyGems gets it from 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
- https://slsa.dev/spec/v1.0/provenance (standard)
- https://slsa.dev/spec/v1.0/levels (standard, Build L1: Provenance exists)
- https://csrc.nist.gov/pubs/sp/800/218/final (standard, PS.3.2: Collect, safeguard, maintain, and share provenance data for all components of each software release)
- https://fleetlint.org/baseline/#releases
Generated by fleetlint docs from catalog v0.7.0.