release/provenance
Releases attest build provenance
| Severity | warning |
| Tiers | 1 |
| Stacks | any |
| Scope | root |
| Kind | outcome |
| Source | library v0.1.0 |
| Selected by | fleetlint-recommended@v0.1.0 |
Requirement
The release pipeline produces a provenance attestation: actions/attest-build-provenance, the SLSA generator, cosign attest, npm provenance (--provenance, or trusted publishing with id-token: write), PyPI attestations from pypa/gh-action-pypi-publish with trusted publishing, docker/build-push-action v4 or newer (provenance is on unless provenance: false), or GitLab’s artifact provenance (RUNNER_GENERATE_ARTIFACTS_METADATA: "true").
Why
Provenance ties the artifact to the exact source and workflow that built it, which a signature alone does not.
Applies when
release.exists && tagged_workflows().size() > 0Fix
Add actions/attest-build-provenance (GitHub), RUNNER_GENERATE_ARTIFACTS_METADATA: "true" (GitLab) or cosign attest --predicate (Gitea) to the release pipeline.
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.
See: https://fleetlint.org/baseline/#releases
Generated by fleetlint docs from catalog v0.1.0.