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

release/signing

Release artifacts are signed

A capability keyed by published artifact: each kind the release publishes is checked by its own implementation, and every one must pass. Implemented for android-app, apple-app, crate, gem, helm-chart, image, maven, npm, nuget, oci-artifact, pub, pypi, release-files.

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

Requirement

Every artifact a release publishes is signed, 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. Each artifact kind’s implementation says what counts for it.

Why

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

Applies when

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

Fix

Sign each published artifact in its own format (fleetlint explain release/signing/<artifact>); 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 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.

Sources


Generated by fleetlint docs from catalog v0.7.0.