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

release/signing/pypi

Release artifacts are signed

Implements release/signing for the pypi artifact: it runs when the release publishes one (see artifacts).

Severityerror
Tiers1
Artifactpypi
Scoperoot
Kindoutcome
Sourcelibrary v0.3.1
Selected byfleetlint-recommended@v0.3.1

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() > 0

Fix

Publish with pypa/gh-action-pypi-publish and trusted publishing (id-token: write); it uploads Sigstore attestations.

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.

See: https://fleetlint.org/baseline/#releases, https://docs.pypi.org/attestations/


Generated by fleetlint docs from catalog v0.3.1.