fleetlint Policy for a fleet of repositories
v0.5
Getting started

release/signing/any

Release artifacts are signed

The stack-neutral implementation of release/signing: it checks stacks without an implementation of their own and repositories where no stack is detected, and its satisfiers count for every stack.

Severityerror
Tiers1
Stacksany
Scoperoot
Kindoutcome
Sourcelibrary v0.2.0
Selected byfleetlint-recommended@v0.2.0

Requirement

The release signs its artifacts with cosign (keyless OIDC on GitHub and GitLab, key-based on Gitea), GoReleaser signs:, or a detached gpg signature, and publishes the signatures with it. A container image is signed by digest with cosign sign.

Why

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

Capability applies when

release.exists && tagged_workflows().size() > 0

Fix

Sign with the stack’s own format (fleetlint explain release/signing/<stack>); without one, add a cosign step to the release workflow: cosign sign-blob for checksums.txt when the release is files, cosign sign <image>@<digest> for a container image (keyless on GitHub, with a key on Gitea).

Agent instruction: Use the stack’s signing format when the stack 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.

See: https://fleetlint.org/baseline/#releases


Generated by fleetlint docs from catalog v0.2.0.