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

release/signing/release-files

Release artifacts are signed

Implements release/signing for the release-files artifact: it runs when the release publishes one (see artifacts).

Severityerror
Tiers1
Artifactrelease-files
Scoperoot
Kindoutcome
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

Requirement

The workflow that uploads the release files signs them or their checksums file (checksums.txt, SHA256SUMS): cosign keyless on GitHub and GitLab, key-based on Gitea, GoReleaser signs: or binary_signs:, or a detached gpg signature, and publishes the signatures with the release.

Why

Checksums prove integrity; only a signature proves who built it.

Capability applies when

release.exists || repo.artifacts.size() > 0

Fix

Add sigstore/cosign-installer and cosign sign-blob --yes --bundle checksums.txt.sigstore.json checksums.txt to the release workflow (or signs: in .goreleaser.yaml) and upload the bundle with the release.

Agent instruction (from release/signing): Use the artifact’s own signing format when it has one. Otherwise add sigstore/cosign-installer and a signing step after the artifacts are built. Files: cosign sign-blob --yes --bundle checksums.txt.sigstore.json checksums.txt and upload the bundle. Container image: cosign sign --yes <image>@<digest> using the digest output of the build step, with id-token: write on the job.

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.