PyPI's redesigned project pages with clearer security signals are now live - The Python Package Index Blog

Open original

PyPI has launched a redesigned project page with a new Security tab that explains where each package file came from, using attestations and provenance states. It also adds warnings for suspicious publishing changes, like a package switching build sources or losing its attestations.

  • Each release is labeled Full Provenance (every file has an attestation) or No Provenance (none do), with the note that no provenance doesn't automatically mean malicious.
  • Six warning types flag mismatches: incomplete, inconsistent, change of, and loss of provenance, plus late file warnings for files uploaded more than 14 days after release.
  • The work was funded by the OpenSSF and built with Kabu Creative, following the OpenSSF Attestations Style Guide, and grew out of user research with the Python community.

PyPI has finished its redesign of project pages, and the headline change is a new Security tab that tells you where a release's files came from. Each release gets a provenance state. "Full Provenance" means every file carries an attestation, either a PyPI Publish attestation confirming a Trusted Publisher uploaded it or a SLSA Build Provenance attestation tying the file to an exact source commit, build platform, and build instructions. "No Provenance" means no file has one, which is typical of older releases and projects that haven't set up Trusted Publishing. The article is careful to say that no provenance doesn't mean malicious, only that the origin can't be cryptographically verified, so you should lean on maintainer history, release patterns, and repo activity instead. The more useful part for anyone installing packages is the set of provenance warnings. "Incomplete Provenance" means some files have attestations and others don't, such as wheels published through Trusted Publishing alongside a source tarball uploaded with an API token. "Inconsistent Provenance" means files in one release came from different build systems or repositories. "Change of Provenance" flags a release built from a different repo or workflow than before, which can be a legitimate migration or a sign of a compromised pipeline. "Loss of Provenance" flags a project that used to attest its releases and suddenly stopped. Each warning comes with a suggested check: read the release notes, look at the issue tracker, or confirm through official channels before installing. The warnings now appear at the top of the project page, though a quarantine banner overrides everything else when it applies. Beyond security, the page layout changed in smaller ways. Metadata is now sorted by usefulness and labeled "PyPI data" or "Data verified by PyPI." The release files tab gained search and filtering, shows per-file provenance, and marks "late" files with an orange icon. Late-file warnings apply to files uploaded more than 14 days after the release timestamp, but only to releases from before July 2026, since a policy then began rejecting such uploads. The release history tab now shows file count, provenance state, and status such as quarantined, yanked, archived, or pre-release. PyPI also extended its package security guide and published a case study in the OpenSSF Attestations Style Guide. The work was funded by the Open Source Security Foundation and built with Kabu Creative.

Ask about this article