release/provenance/helm-chart
Releases attest build provenance
Implements release/provenance for the helm-chart artifact: it runs when the release publishes one (see artifacts).
| Severity | warning |
| Tiers | 1 |
| Artifact | helm-chart |
| Scope | root |
| Kind | outcome |
| Source | library v0.3.1 |
| Selected by | fleetlint-recommended@v0.3.1 |
Requirement
A chart pushed to an OCI registry gets provenance attached to its digest (cosign attest, actions/attest-build-provenance with subject-digest); a chart in a chart repository gets an attestation on the packaged file (cosign attest-blob).
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() > 0Fix
After helm push, run cosign attest --yes --type slsaprovenance --predicate provenance.json <registry>/<chart>@<digest>, or add actions/attest-build-provenance with the chart’s digest.
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.
See: https://fleetlint.org/baseline/#releases, https://slsa.dev/spec/v1.0/provenance
Generated by fleetlint docs from catalog v0.3.1.