Attestations: a new generation of signatures on PyPI
summary
PyPI implements attestations from PEP 740: machine‑readable signed statements, short‑lived identity binding via a signing service, and a transparency log so uploads force visibility. Implementation is deployed and used by default in GitHub Actions pip publish; adoption is already nontrivial — 14% of uploads since the MVP and one in five of the top‑360 packages have attestations. Verification is index‑side today; local default end‑user verification and broader verifier adoption remain work in progress.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:23Code signing motivation
- 10:01PGP signing problems
- 13:12New signing design
- 18:00PEP 740 implementation
- 19:03Attestations adoption
- 21:50Auditability benefits
- 22:51End-user verification challenges
- 24:37Default verification goals
- 26:19Key takeaways
- 27:24Q&A
related talks
31mPEP 740 and PyPI: Bootstrapping Provenance for the Python Ecosystem
36mWhere Does Your Software (Really) Come from?
19mSecuring Packages in npm, Homebrew, PyPI, Maven Central, and...
54mFrom "Trust Me" to "Verify Me"
39mAuthenticating Supply-chain Metadata: Building Remote Code Attestations on GitHub
46mEnhancing Artifact Security with GitHub’s Build Provenance...
33mAttesting and Verifying Your Software Supply-Chain With In-toto
38mThe Telemetry of Trust, Using Attestations to Secure Your SDLC...