PyPI project pages now have a Security tab showing whether release files carry digital attestations.
- A PyPI Publish attestation names the Trusted Publisher that uploaded the file. A SLSA Build Provenance attestation ties it to a source commit, build platform and build instructions.
- Full provenance means every file has at least one attestation. No provenance is common for older releases, and that doesn’t make them malicious.
- PyPI warns when only some files are attested, when a release comes from a different repo or workflow than before, or when a project that used to attest stops. Those warnings sit at the top of the project page.
My take
The “workflow changed” warning is the one I’ll watch. That’s exactly what a hijacked pipeline looks like, like the bee-js mess today on npm. Use it alongside pinned hashes, which I walk through in today’s how-to.
God Bless, and May the Source Be with You!
