release/signing/crate
Release artifacts are signed
Implements release/signing for the crate artifact: it runs when the release publishes one (see artifacts).
| Severity | error |
| Tiers | 1 |
| Artifact | crate |
| Scope | root |
| Kind | expr |
| Source | library v0.6.0 |
| Selected by | fleetlint-recommended@v0.6.0 |
Requirement
crates.io has no package signatures yet; a crate is checked for trusted publishing (release/trusted-publishing/crate), and binaries built from it as release files.
Why
Checksums prove integrity; only a signature proves who built it.
Capability applies when
release.exists || repo.artifacts.size() > 0Applies when
falseCheck
trueFix
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
- https://csrc.nist.gov/pubs/sp/800/218/final (standard, PS.2.1: Make software integrity verification information available to software acquirers)
- https://github.com/ossf/scorecard/blob/main/docs/checks.md (standard, Signed-Releases)
- https://fleetlint.org/baseline/#releases
Generated by fleetlint docs from catalog v0.6.0.