PyPI now warns you when a package's origin can't be verified

PyPI's redesigned project pages with clearer security signals are now live

PyPI now warns you when a package's origin can't be verified

PyPI has finished its UI overhaul, adding a dedicated security tab that shows each release's provenance state and per-file attestations. Releases with full provenance have every file backed by PyPI Publish or SLSA Build Provenance attestations; those without get a clear notice that file origin can't be cryptographically verified. New warnings flag incomplete, inconsistent, changed, or lost provenance, and the project page, release files, and release history tabs were redesigned around them.

"No provenance" simply means that no file in the release has an attestation. This is typical for older releases or projects that have not yet configured Trusted Publishing.
  1. time4tea

    Not very keen that the whole story of trust is basically centralisation - requiring "big cloud" and essentially promoting lock-in.

    Did I get that right? Seems a bit anti-pythonic.

  2. djoldman

    Some examples:

    dlt (no provenance): https://pypi.org/project/dlt/#files

    datasette (yes provenance): https://pypi.org/project/datasette/#files

  3. samhclark

    This is great! I want sigstore-based or at least sigstore-style "keyless" short lived signatures to become more and more popular, so that support gets better everywhere. In particular, if having secure OIDC handling in a CI/CD pipeline becomes something that keeps people on GHA or GitLab then I'd hope third-party hosted CI/CD services begin to take that gap seriously and work on meeting those requirements.

    I'm bought in on keyless signing, and I want there to be many more providers, so I like to see more adoption which builds more momentum.

  4. cowlevel

    This is about detecting formerly benign projects that have had their pypi entries hacked, but not their private keys. It does not detect malicious projects.

  5. mhils

    Very cool to see PyPI put more emphasis towards exposing provenance info. It would be even cooler if trusted publishing would finally support reusable workflows (https://github.com/pypi/warehouse/issues/11096).

  6. pasteleft

    Are these security signals also available in pip??

    I don't really look into PyPI package page before typing pip install numpy.

  7. eesmith

    Am I correct in my understanding that the only trusted publishers are for-profit US companies? And these all use proprietary implementations which cannot easily be replicated elsewhere?

    Like, if I want to host on Codeberg, or Sourcehut, what is the process needed for those platforms to become a trusted publisher?

    As it happens, I build my releases on my own hardware using a pypa/manylinux release. Can I provide attestation, or am I required to use a third-party service to get that "x Without provenance" removed from my entry?

  8. darkamaul

    Not directly the subject but they switched from Material for MkDocs to Zensical.

    It’s quite sad to see that one of the main (or the biggest?) documentation system for the Python completely alienated its user base and led to this fork.

More from this day

2026-11-14