Sigstore for Python Packaging: Next Steps for Adoption
summary
Trail of Bits spends nine months building sigstore-python, a CLI and API that signs and verifies Python distributions, uses OpenID Connect for ambient credentials (GitHub Actions, Google Cloud Build), and is already used to sign CPython 3.11 and CI artifacts daily. It delivers sig and cert files to GitHub releases but does not yet integrate with PyPI or pip: PyPI must accept .sig/.cert or Sigstore bundles and pip must move from PEP 503 to the newer index and support PEP 458/TUF-backed verification for end-to-end trust.
AI-written summary · about
chapters (4)
- 0:00Start
- 10:18python package security: integrity
- 11:49python package security: authenticity
- 13:53what does sigstore do for python packaging?
related talks
35mAn introduction to Sigstore for Pythonistas
29mErgonomic codesigning for the Python ecosystem with Sigstore
01h 21mSecure Python Packaging & Release Using Continuous Deployment
31mPEP 740 and PyPI: Bootstrapping Provenance for the Python Ecosystem
35mSecuring Python projects Supply Chain
25m"Security considerations in Python Packaging"
24mShipping your first Python package and automating future publishing
34mSecure Python Development: Tips, Tricks, and Tools
