fleetlint Policy for a fleet of repositories
v0.11 (latest)
Getting started

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).

Severitywarning
Tiers1
Artifacthelm-chart
Scoperoot
Kindoutcome
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

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() > 0

Fix

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 (from release/provenance): Use the registry’s own provenance where it has one: npm publish --provenance, pypa/gh-action-pypi-publish or rubygems/release-gem with trusted publishing, from a job with id-token: write. Otherwise add a step uses: actions/attest-build-provenance with subject-path covering the built files (or subject-name and subject-digest for an image or a chart in a registry, 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.

A finding that names no file points at the first workflow that publishes the artifact, or .github/workflows/release.yml when there is none.

Sources


Generated by fleetlint docs from catalog v0.8.0.