A stylized illustration of a Python package page with a shield and a security checklist, representing PyPI's new Security tab

The Python Package Index has redesigned its project pages, and the most useful change is a new Security tab on every project detail page. It shows, release by release, whether the files you are about to install carry a verifiable record of where they came from. The change went live in November 2026, and it turns a question developers used to guess at into one you can now answer in seconds.

Here is the 30-second check. Open the project page, look at the sidebar for the provenance state, and click the Security tab. If every file in the release is attested, you have full provenance. If nothing is attested, or a warning is showing, slow down and read the details before you run pip install. The rest of this guide explains what each state and warning means, and what to do about it.

What the Security Tab Shows and Where to Find It

The Security tab sits on every PyPI project detail page, next to the tabs you already know. It lists each release and its provenance state, and it shows the attestations attached to individual files. An attestation is a digital record of a release file's provenance — where it came from. PyPI introduced digital attestations in 2024, but until now they were hard to find unless you knew exactly where to look.

There are two kinds of attestation. A PyPI Publish attestation means the file was published by a PyPI Trusted Publisher. An SLSA Build Provenance attestation links the file to its exact source commit, the build platform, and the build instructions. Together they let you check that the file on PyPI is the file the project's own build produced, rather than something uploaded by hand from an unknown machine.

The redesign was announced on the PyPI blog on November 6, 2026, in a post by Nicole Harris. The work had been announced in July 2026 and was shaped by user research with Python community members. It was funded by the Open Source Security Foundation (OpenSSF) and implemented by Kabu Creative, following the OpenSSF Attestations Style Guide.

Two more small changes help you read the page. Metadata is now ordered by utility, and each item is labelled either "PyPI data" or "Data verified by PyPI", so you can tell at a glance what PyPI itself has checked. The sidebar also shows the release's provenance state and links straight to the Security tab, so you do not need to hunt for it.

The Two Provenance States

Every release falls into one of two provenance states. The state is a summary of the release's files, not a verdict on the project as a whole. A project can have full provenance on one release and no provenance on the next, which is why the check is worth doing per release, not once per project.

Provenance state What it means What to do
Full Provenance 100% of the release files have attestations Proceed as normal, and still read the release notes and check the version you need
No Provenance No file in the release has an attestation Do not assume the worst, but check the surrounding trust signals before installing

Full Provenance is the good case. Every file in the release carries an attestation, so the origin of each file is cryptographically verifiable. That does not prove the code is bug-free or safe to run — it proves the files came from the project's stated build. It is a strong signal, and it is the one to look for first.

No Provenance is the common case for older projects and for many small ones. It means no file in the release has an attestation, so the file origin cannot be cryptographically verified. That is all it means. It is not a finding of malware, and PyPI does not present it as one.

The Four Provenance Warnings

Between the two clean states sit four warnings. Each one describes a specific pattern in a release's files, and each has legitimate explanations as well as suspicious ones. PyPI presents them as something worth checking, not as proof of compromise. Your job is to look at the context and decide whether the explanation fits.

Warning What it means What to do
Incomplete Provenance Some files are attested and others are not Check which files lack attestations and how they were uploaded
Inconsistent Provenance Files in one release come from different build systems or source repositories Ask whether the split matches a known migration or split build
Change of Provenance Release files come from a different repository or workflow than a previous release Look for a rename, migration, or new workflow before assuming foul play
Loss of Provenance The project previously published with attestations and now uploads without them Treat this as the warning most worth a pause, and check the project's recent history

Incomplete Provenance

Incomplete Provenance means some files in the release are attested and others are not. A typical example is a release where the wheels were published through Trusted Publishing, but the source tarball was uploaded with an API token instead. The attested files are verifiable; the unattested ones are not.

When you see this warning, look at which files are missing attestations. If the file you actually need — usually a wheel for your platform — is attested, the risk is lower than if the unattested file is the one you would install. If the missing attestation covers the file you need, check the project's release history and repository before deciding.

Inconsistent Provenance

Inconsistent Provenance means the files in a single release came from different build systems or different source repositories. One wheel might trace back to one workflow while another traces back to somewhere else entirely. That split is unusual enough to flag, because a normal release usually comes from one build.

The right response is to ask whether the split has a boring explanation. A project mid-migration between build systems can produce exactly this pattern. If there is no visible migration, no changelog note, and no repository activity explaining it, treat the release with more caution and consider pinning an earlier release you trust.

Change of Provenance

Change of Provenance means the release files came from a different repository or workflow than a previous release. This often has a legitimate cause: an organisation rename, a repository migration, or a switch to a new release workflow. All three are common in long-lived projects, and all three change the provenance trail.

But the same pattern can also indicate a compromised pipeline or an account takeover, which is why PyPI flags it. The check is straightforward: look for evidence of the change in the open. A renamed organisation, a moved repository, or a new workflow file in the source repo supports the innocent explanation. Silence does not.

Loss of Provenance

Loss of Provenance is the warning to take most seriously. It means the project previously published releases with attestations, and now it is uploading releases without them. Something changed, and the change went in the wrong direction: a project that used to prove its files' origin has stopped doing so.

There can still be an innocent reason, such as a broken release workflow that nobody has fixed yet. Even so, pause before installing. Check the project's recent commits, issues, and release notes for any mention of the change, and prefer an earlier attested release until the project explains what happened.

Where Warnings Appear on the Page

Provenance warnings appear at the top of the project page, alongside the banners for yanked, archived, and pre-release versions. That placement is deliberate: you see the warning before you scroll to the install command. A quarantine banner overrides all of them, so if a release is quarantined, that is the message that takes priority.

This is a real improvement over the old layout, where attestation information was buried. The story clearly struck a chord: it reached the Hacker News front page on November 14–15, 2026, with around 250 points and about 106 comments. A summary of the new Security tab walks through the same changes for readers who want a second overview of what moved and why.

What "No Provenance" Does NOT Mean

The most common misreading of the new tab is also the most damaging one: treating No Provenance as a sign that a release is malicious. It is not. It means the file origin cannot be cryptographically verified, nothing more. Most packages on PyPI predate attestations or have never set them up, and the vast majority are perfectly ordinary software.

When a release has no provenance, rely on the surrounding trust signals instead. Look at the maintainer history: is this a long-standing project with a consistent maintainer, or a new account with a single release? Look at the release pattern: steady, versioned releases over time, or a sudden burst? And look at repository activity: recent commits, issues being answered, and a changelog that matches the release.

The same caution applies in reverse. Full Provenance does not mean a package is safe to run. It means the files came from the project's stated build. If the project's own source code is compromised, or if a maintainer account is taken over and the build itself is poisoned, the attestation will faithfully record that poisoned build. Provenance answers "where did this come from?", not "is this code trustworthy?"

The Redesigned Release Files and Release History Tabs

The Security tab is the headline, but the two tabs next to it got useful upgrades too. The redesigned Release Files tab now has search and filtering, so you can find the exact file for your platform without scrolling a long list. It also has a per-file provenance column, so you can see at a glance which files are attested and which are not.

Watch for the orange late-file icons in that tab. They mark files uploaded more than 14 days after the release timestamp. A file added weeks after a release deserves a question: why was it added so late? These warnings only appear on releases from before July 2026, when PyPI started rejecting new files uploaded more than 14 days after the release timestamp.

The Release History tab now shows the file count, the provenance state, and the release status for each version — quarantined, yanked, archived, or pre-release. That makes it much easier to scan a project's history and spot the odd one out: the release with fewer files than its neighbours, or the one whose provenance state suddenly changed.

PyPI's user documentation was also extended with a package security guide, which walks through these signals in more detail. The change was also covered in This Week in Package Management, which rounds up news from across the packaging ecosystem. If you want the full background after reading this article, that guide is the next place to look.

Your 5-Step Pre-Install Check (Under a Minute)

You do not need a security audit before every pip install. You need a quick routine you will actually do. Here is one that takes under a minute once you know where to look, and it uses the new Security tab as its starting point.

1. Open the Security tab - check the release's provenance state
2. Read any warning - match it to the four warnings above
3. Check the Release Files tab - confirm your file is attested
4. Scan the Release History tab - look for sudden changes
5. Check the source repo - recent activity, maintainer history

Step one is the provenance state in the sidebar or the Security tab. Full Provenance means you can move on quickly. No Provenance means you lean on the other steps. A warning means you read it before anything else, because the warning is telling you exactly what is unusual about this release.

Step two is matching the warning to its meaning. An Incomplete Provenance warning on a file you will not install matters less than the same warning on the wheel you are about to download. A Loss of Provenance warning matters more than the others, because it means a project stopped proving its origin.

Step three is the Release Files tab. Find the file for your platform and check its per-file provenance column. If your file is attested, that is the strongest single signal in this check. If it is not, and the release is old or the project is small, move to step four and five rather than stopping outright.

Step four is the Release History tab. Look for sudden changes: a release with a different provenance state from its neighbours, a version yanked after publication, or a file count that jumps without explanation. Steady history is reassuring; a sharp break in the pattern is worth a closer look.

Step five is the source repository and maintainer history. Recent commits, answered issues, and a changelog that matches the release all support the package. A dormant repository, a brand-new maintainer account, or a release with no matching source activity should make you pause — especially combined with a provenance warning.

Python Package Security Tools That Go Further Than the Security Tab

The Security tab answers one question well: where did this file come from? The best Python package security tools go further, and the good news is that the most useful ones are checks, not products. You can build a solid pre-install routine from the tab itself, PyPI's package security guide, and a few habits that cost nothing.

Start with the Security tab and the package security guide together. The tab shows the provenance state and warnings for the release you are about to install, and the guide explains how to interpret them. That combination — the signal plus the documentation for reading it — is the foundation of the whole routine, and it is available on every project page.

Next, verify package integrity as a habit. Check that the version you are installing matches the version the project announced, and that the release notes describe the changes you expect. If a release appeared without an announcement, a changelog entry, or matching repository activity, that gap is itself a signal worth noticing before you install.

Finally, check the source repository and maintainer history every time the provenance signals are weak or a warning is showing. Look for recent activity, a consistent maintainer, and a release pattern that makes sense. This is the same check that matters when a release has no provenance at all, and it is the check that catches the cases attestations cannot.

The broader lesson is the same one behind this month's other security stories. An Apache HTTP Server RCE and a PostgreSQL security update both rewarded the same habit: read the advisory, check what you are actually running, and act before the next incident. PyPI's Security tab makes that habit easier for Python packages, and it is worth the minute it takes.

One more habit helps outside Python too. When you test an API or a service before trusting it, do it in a way that keeps your data private — the same instinct as keeping your API testing private. The tool changes; the principle does not: check first, install second, and know what you are running.

Frequently Asked Questions

What is the PyPI security tab?

The PyPI security tab is a new tab on every project detail page that shows each release's provenance state and per-file attestations. It was announced on November 6, 2026, as part of a redesign of PyPI project pages. It lets you see whether a release's files carry a verifiable record of where they came from before you install them.

What is package provenance?

Package provenance is a verifiable record of where a release file came from. On PyPI, digital attestations provide that record: a PyPI Publish attestation means the file was published by a PyPI Trusted Publisher, and an SLSA Build Provenance attestation links the file to its exact source commit, build platform, and build instructions.

Does No Provenance mean a package is malicious?

No. No Provenance means no file in the release has an attestation, so the file origin cannot be cryptographically verified. It does not mean the release is malicious. Many legitimate packages have no attestations. When you see it, rely on surrounding trust signals such as maintainer history, release patterns, and repository activity.

What should I do if I see a Change of Provenance warning?

First look for a legitimate explanation, such as an organisation rename, a repository migration, or a new release workflow. Check the source repository for evidence of the change. If there is no visible explanation, treat the release with caution and consider pinning an earlier release you trust until the project explains what changed.

What does Loss of Provenance mean?

Loss of Provenance means a project previously published releases with attestations and now uploads releases without them. It is the warning most worth a pause, because a project that used to prove its files' origin has stopped doing so. Check the project's recent commits, issues, and release notes, and prefer an earlier attested release until it is explained.

What are the best tools to check a Python package before installing it?

The best checks are the PyPI Security tab itself, which shows provenance states and warnings for each release, and PyPI's package security guide, which explains how to read them. Add two habits: verify package integrity by matching the version and release notes to what the project announced, and check the source repository and maintainer history for recent activity and a consistent release pattern.