PyPI launches redesigned UI with clearer security signals and provenance warnings
The Python Package Index has rolled out a new security tab and updated project pages to help developers verify package origins and detect supply chain risks.
The Python Package Index (PyPI) has officially launched a redesigned user interface aimed at making package security signals more visible and understandable. Released in November 2026, these updates introduce a dedicated security tab, provenance warnings, and improved metadata organization to help developers assess the integrity of the libraries they install.
What happened
Following an announcement in July regarding planned interface improvements, the PyPI team has completed a major overhaul of its project pages. The redesign was shaped by user research within the Python community and implemented in partnership with design agency Kabu Creative. The primary goal is to address the growing threat of malicious actors targeting the Python ecosystem by making it easier for users to verify where package files come from.
While digital attestations were introduced in 2024 to provide verifiable records of file provenance, many users found the concepts unfamiliar and the existing interface lacking in clarity. The new updates implement recommendations from the OpenSSF Attestations Style Guide to bridge this gap. By surfacing security data more prominently, PyPI aims to help developers distinguish between verified releases and those with unverified origins without requiring deep cryptographic expertise.
The rollout includes changes to the project detail page, release files tab, and release history tab. These changes are now live for all users. The initiative was funded by the Open Source Security Foundation (OpenSSF), which also published a case study on the design patterns used in this update to benefit the wider open source ecosystem.
How it works
The core of the update is the new security tab, which displays the provenance state of each release. Provenance refers to the verifiable record of where a release file originated. PyPI calculates this state by checking for digital attestations on every file in a release. There are two main states: "Full Provenance," meaning 100% of files have attestations, and "No Provenance," meaning no files have them. Full provenance may include PyPI Publish attestations, which confirm the file was published via a Trusted Publisher, or SLSA Build Provenance attestations, which link the file to its specific source commit and build platform.
To help users spot potential compromises, the system generates specific provenance warnings when metadata looks unusual. An "Incomplete Provenance" warning appears if some files have attestations while others do not, such as when wheels are published via Trusted Publishing but source tarballs are uploaded manually. An "Inconsistent Provenance" warning flags files originating from different build systems or repositories within the same release. A "Change of Provenance" warning indicates that files came from a different repository or workflow than previous releases, which could signal an account takeover or infrastructure migration. Finally, a "Loss of Provenance" warning alerts users if a project that previously used attestations stops doing so.
The project detail page has also been restructured. Provenance warnings now appear at the top alongside other status banners like yanked or archived notices. Metadata in the sidebar is reordered by utility and clearly labeled as either "PyPI data" or "Data verified by PyPI." The release files tab allows users to search and filter files, showing provenance states per file and highlighting late uploads with an orange warning icon. Late files are those uploaded more than 14 days after the initial release timestamp, a policy enforced since July 2026.
Key details
- New Security Tab: Provides a dedicated space to view release provenance states and per-file attestations, replacing scattered security information.
- Provenance Warnings: Four specific warning types (Incomplete, Inconsistent, Change, Loss) help identify potential supply chain attacks or configuration errors.
- Full vs. No Provenance: "Full Provenance" means all files have cryptographic attestations; "No Provenance" means none do, which is common for older packages but implies unverified origin.
- Late File Alerts: Files uploaded more than 14 days after the initial release timestamp are marked with an orange warning icon, applicable to releases prior to July 2026.
- Redesigned Metadata: Sidebar data is now ordered by utility rather than verification status, with clear labels distinguishing PyPI-verified data from other metadata.
- OpenSSF Collaboration: The design follows the OpenSSF Attestations Style Guide, and a case study has been published to share these patterns with the broader ecosystem.
Why it matters
For software engineers and technical leads, the supply chain is a critical attack vector. Malicious packages often mimic legitimate ones or compromise existing accounts to distribute malware. Previously, verifying the integrity of a package required manual checks of build logs or external tools. The new PyPI interface brings these verification steps directly into the browsing experience, reducing the friction needed to make secure choices. This is particularly important for teams managing large dependency trees, where a single compromised library can impact entire applications.
The distinction between "No Provenance" and malicious intent is crucial. Many legitimate, older projects do not use Trusted Publishing or attestations. The new UI clarifies that lack of provenance does not equal malice, but rather a lack of cryptographic verification. This nuance helps developers avoid false positives while still encouraging maintainers to adopt modern security practices like Trusted Publishing. By making these signals visible, PyPI incentivizes the ecosystem to move toward verifiable builds.
Furthermore, the provenance warnings serve as an early detection system for account takeovers. If a maintainer’s account is compromised, attackers often publish from different workflows or repositories. The "Change of Provenance" and "Inconsistent Provenance" warnings can alert users to these anomalies before they install a potentially harmful version. This shifts some of the burden of vigilance from the user to the platform, providing automated cues that something may be wrong.
What you can do
- Check the Security Tab: When evaluating a new package, visit the security tab to see if it has Full Provenance or if there are any active warnings.
- Investigate Warnings: If you see a provenance warning, check the project’s release notes or issue tracker to confirm if the change was intentional, such as a repository migration.
- Adopt Trusted Publishing: If you maintain a package, configure Trusted Publishing with a publisher that generates attestations to achieve Full Provenance status for your releases.
- Review Late Files: Be cautious of releases with late file warnings, especially for older packages, as these may indicate post-release tampering or irregular publishing practices.
- Read the Documentation: Consult PyPI’s updated package security guide to learn how to assess source code security and verify package integrity effectively.
- Provide Feedback: Participate in community discussions or report issues if you encounter confusing security signals, helping the PyPI team refine the experience further.



