1-minute read of a 3 min report

PyPI puts release-file provenance warnings on project pages

By

1-minute read

What a defender needs to know

PyPI’s redesigned project pages now place release-file attestations and provenance warnings in a Security tab. The release-files table also shows each file’s state, so a reviewer can check the wheel or source archive an installer will use. A release with full provenance has attestations on every file; incomplete provenance means only some files have them.

A changed repository or build workflow, a mix of origins within one release, or the loss of previously present attestations warrants a pause before a dependency update. Read the file’s attestation metadata and, where useful, its transparency-log link. Compare the named repository and workflow with prior releases and the maintainers’ release notes or official channels. Hold the update and ask the project if the change remains unexplained. PyPI says older releases and projects without Trusted Publishing commonly have no provenance; a missing attestation alone is not a malicious-code finding. An attestation verifies a file’s stated origin, so source review remains a separate step.

Maintainers can configure Trusted Publishing with a CI identity that produces attestations for future uploads. After the next release, check every file in PyPI’s Security tab; the expected result is provenance from the intended repository and workflow for each attested file. Investigate an unexpected missing attestation or origin before promoting that release.

Primary sources