PyPI launches redesigned project pages with a Security tab for provenance

PyPI launches redesigned project pages with a Security tab for provenance

The PyPI team has announced that the user interface overhaul it first described in July is complete and live on PyPI. Shaped by user research with members of the Python community, the update aims to improve how PyPI surfaces security signals and displays package details.

The team's reasoning: with the rapid growth of the Python ecosystem, PyPI has become an increasingly attractive target for malicious actors, and the team has been shipping security features and taking a more active role in helping users assess package security. Digital attestations, introduced in 2024, give a verifiable record of a release file's provenance, meaning where it came from. But provenance and attestations are still unfamiliar to many PyPI users, and the old interface did little to explain their meaning, importance or limitations. PyPI partnered with Kabu Creative to fix that, implementing recommendations from the OpenSSF Attestations Style Guide.

The centrepiece is a new Security tab. It shows a release's provenance state and the attestations for each file. PyPI calculates the state by checking whether each release file has an attestation. Typically a release is in one of two states. "Full Provenance" means 100% of the release files have attestations, of either or both supported types: PyPI Publish attestations, which confirm the file was published by a PyPI Trusted Publisher, and SLSA Build Provenance attestations, which link the file to its exact source commit, build platform and instructions. Users can read attestation metadata in the UI or follow the transparency log link. "No Provenance" means no file in the release has an attestation. That is typical for older releases or projects that have not set up Trusted Publishing. It does not necessarily mean a release or file is malicious; it means the file's origin cannot be cryptographically verified. In that case PyPI advises relying on surrounding trust signals such as maintainer history, release patterns and repository activity, and asks maintainers to consider Trusted Publishing with a publisher that generates attestations for their next release.

Provenance warnings are meant to show when a file may not have come from the project's maintainers, for example after an attacker takes over an account or a publishing workflow. PyPI shows a prominent warning when provenance metadata looks unusual or conflicts with a project's history. Many warnings have legitimate explanations, but each is worth checking before installing. There are four:

  • Incomplete Provenance: some files carry attestations and others do not, for instance wheels published via Trusted Publishing but a source tarball uploaded with an API token. PyPI suggests checking release notes for build issues or asking in the project's issue tracker before installing.
  • Inconsistent Provenance: files in the same release come from different build systems or source repositories. Users should check the attestation metadata to confirm all files came from sources the maintainers control.
  • Change of Provenance: the files came from a different repository or workflow than a previous release. This is often legitimate, such as an organisation rename or repository migration, but can also point to a compromised pipeline or account takeover. Users should check release notes or official channels for a planned migration.
  • Loss of Provenance: a project that used to publish with attestations now uploads files without them. Users should check whether the maintainers changed their process on purpose, for example by going back to API tokens. If it is unexpected, PyPI says to treat the release with skepticism until verified.

The project detail page was reworked to support this. Provenance warnings now sit at the top, next to banners for yanked releases, archived projects and pre-releases; if a project or release is quarantined, only the quarantine banner shows, because it takes precedence over all others. When a release has full provenance or warnings, its state appears in the sidebar and links to the Security tab. Metadata is now ordered by usefulness and labelled "PyPI data" or "Data verified by PyPI", replacing the old grouping by verification status.

The release files tab can now search and filter long lists, shows the provenance state of each file, and marks late files with an orange warning icon. A late file warning appears when one or more files were uploaded more than 14 days after the initial release timestamp. These warnings appear only on releases from before July 2026, when PyPI introduced a policy of rejecting new files after 14 days. The release history tab now also shows file count, provenance state and release status (quarantined, yanked, archived or pre-release).

PyPI also extended its user documentation with a package security guide covering how to assess source code security, check provenance, verify package integrity, protect against common attacks and report security issues. The Security tab is meant as a permanent home for future attestation types and security notices, and the team published a case study of the design patterns and warnings in the OpenSSF Attestations Style Guide.

The initiative was funded by the Open Source Security Foundation (OpenSSF) and implemented by Kabu Creative. The team thanks Dustin Ingram, Zach Steindler and the OpenSSF Securing Software Repositories Working Group for championing it; Mike Fiedler, Jacob Coffee and members of the PyPI team for design feedback and code reviews; @cofiem for contributions to the release files tab; and the user interview participants and community testers.

Key facts

  • A new Security tab on PyPI project pages shows each release's provenance state and per-file attestations. The redesign was announced in July and is now live.
  • "Full Provenance" means 100% of a release's files carry attestations, either PyPI Publish (Trusted Publisher) or SLSA Build Provenance, or both. "No Provenance" means none do, and PyPI says that does not by itself mean the release is malicious.
  • Four warnings flag odd publishing patterns: Incomplete, Inconsistent, Change of and Loss of Provenance. The last two can indicate a compromised pipeline or account takeover, though the causes are often legitimate.
  • The release files and release history tabs gained search, filtering, per-file provenance state and release status. Late file warnings (uploads more than 14 days after the initial release) appear only on releases from before July 2026.
  • The work was funded by the OpenSSF and implemented by Kabu Creative, following the OpenSSF Attestations Style Guide.

Why it matters

Digital attestations have existed on PyPI since 2024, but PyPI says provenance is still unfamiliar to many users and the old interface did little to explain it. The redesign moves that information to a dedicated Security tab and a sidebar indicator, and adds warnings for cases such as a project that stops publishing with attestations. PyPI frames this as a response to the Python ecosystem becoming an increasingly attractive target for malicious actors. The Security tab is also meant to host future attestation types and security notices.

Who it affects

Anyone who installs or evaluates packages from PyPI, who now sees provenance states and warnings on project pages. Package maintainers are affected too: PyPI suggests they consider Trusted Publishing with a publisher that generates attestations for their next release, and changing how they publish (for example, going back to API tokens) can trigger a Loss of Provenance warning.

How to use it

Open a project's Security tab to see the release's provenance state and per-file attestations, and follow the transparency log link for more detail. If you see a warning, check it before installing. For Incomplete Provenance, read the release notes or ask in the issue tracker. For Inconsistent Provenance, check the attestation metadata. For Change of Provenance, look for an announced migration. For Loss of Provenance, find out whether the maintainers changed their process on purpose, and treat the release with skepticism until verified if it is unexpected. With no provenance, look at maintainer history, release patterns and repository activity. PyPI's extended documentation includes a package security guide.

How solid is it

This is a first-party announcement from the PyPI team on its own blog, describing features that it says are live. The design follows the OpenSSF Attestations Style Guide, and the changes were shaped by user research with Python community members. The post gives no adoption figures, such as how many packages or releases carry attestations, and gives no results from the user research.

Risks and caveats

No provenance does not mean a release is malicious; it means the origin cannot be cryptographically verified, and it is typical for older releases and projects without Trusted Publishing. Warnings have many legitimate explanations, such as an organisation rename or repository migration, so they call for checking rather than automatic rejection. Conversely, a Change of Provenance can also signal a compromised pipeline or account takeover. Late file warnings appear only on releases from before July 2026, when the 14-day policy for new files began.