release/signing/pypi
Release artifacts are signed
Implements release/signing for the pypi artifact: it runs when the release publishes one (see artifacts).
| Severity | error |
| Tiers | 1 |
| Artifact | pypi |
| Scope | root |
| Kind | outcome |
| Source | library v0.8.0 |
| Selected by | fleetlint-recommended@v0.8.0 |
Requirement
Wheels and sdists carry PyPI attestations (pypa/gh-action-pypi-publish with trusted publishing, which attests by default) or are signed with sigstore-python.
Why
Checksums prove integrity; only a signature proves who built it.
Capability applies when
release.exists || repo.artifacts.size() > 0Fix
Publish with pypa/gh-action-pypi-publish and trusted publishing (id-token: write); it uploads Sigstore attestations.
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
- 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
- https://docs.pypi.org/attestations/ (spec)
Generated by fleetlint docs from catalog v0.8.0.