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

release/signing

Release artifacts are signed

A capability: each stack checks it with its own tools. Implemented for any, dotnet, flutter, java, kotlin, node, python, ruby.

Combine: any. One implementation passing is enough: this belongs to the repository, not to each stack, so the stack that does it decides and the others pass with it.

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

Requirement

Every release signs its artifacts, with the signature its ecosystem already checks where there is one (an Android app’s APK signature, PGP for Maven Central, npm provenance, PyPI attestations, NuGet package signing), otherwise with cosign or gpg. Signatures are published with the release. A container image is signed by digest with cosign sign, whatever the stack.

Why

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

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.