Quick Answer: PyPI package provenance is a cryptographically verifiable record of where a release file was built and published. PyPI's redesigned project pages now surface it in a dedicated Security tab. "Full Provenance" means every file carries an attestation. "No provenance" doesn't mean malicious; it means the file's origin can't be verified. Provenance warnings flag unusual changes worth checking before you install.
Installing a package from PyPI means trusting someone you've probably never met. PyPI package provenance is the mechanism built to shrink that gap. The platform has now finished a planned interface overhaul, shaped by user research with Python community members, and the new security signals are live on every project. The goal is simple: make "did this file really come from the maintainers?" answerable without a supply-chain security background.
What Changed on PyPI Project Pages
In July, PyPI announced a series of interface updates. As the PyPI team's post confirms, that work is now complete. The changes build on digital attestations, which PyPI introduced in 2024 to give each release file a verifiable record of where it came from.
The problem was communication. Attestations existed, but the interface did little to explain what they meant, why they mattered, or where they fell short. PyPI worked with Kabu Creative to implement recommendations from the OpenSSF Attestations Style Guide. The result is a Security tab on each project detail page, with provenance states and per-file attestation metadata in one place.
Here's the part that matters most: the Security tab doesn't just show a green check. It shows you a state, and that state changes how you should read everything else on the page.
How Provenance States Work (and What "Full" Really Proves)
PyPI calculates each release's provenance state by checking whether each release file has an attestation. In practice, a release lands in one of two states.
Full Provenance means 100% of the release files have attestations. Those attestations can be one or both of two types:
- PyPI Publish attestations confirm the file was published by a PyPI Trusted Publisher, meaning an identity-verified CI workflow rather than a long-lived API token.
- SLSA Build Provenance attestations link the file back to its exact source commit, build platform, and build instructions, following the SLSA framework.
You can inspect attestation metadata directly in the UI, or follow the transparency log link to verify the record independently.
Now the catch. Attestations tell you where a file was built, not whether the code inside is safe. If an attacker compromises a repository and that repository builds through its normal workflow, the resulting release can still carry a valid attestation. Full provenance raises your confidence in the publishing path. It doesn't replace reading the code or checking the maintainer's track record.
No Provenance means no file in the release has an attestation. This is typical for older releases and for projects that haven't configured Trusted Publishing yet.
Provenance Warnings: Four Patterns Worth Checking
Warnings appear when provenance metadata looks unusual or conflicts with a project's history. Many have legitimate explanations, but each one deserves a look before you install.
- Incomplete Provenance: Some files have attestations and others don't. A common example is wheels published through Trusted Publishing while the source tarball went up with an API token. Check the release notes for build problems, or ask in the issue tracker.
- Inconsistent Provenance: Files in the same release come from different build systems or source repositories. Confirm in the attestation metadata that every file traces back to infrastructure the maintainers control.
- Change of Provenance: The release came from a different repository or workflow than the previous one. Organization renames and repository migrations cause this routinely. A compromised pipeline can look exactly the same from the outside, so confirm the migration was announced through official channels.
- Loss of Provenance: A project that used to publish attestations now uploads files without them. The maintainers may have switched back to API tokens on purpose. If you didn't expect it, treat the release with skepticism until someone verifies it.
Most people treat warnings as a yes-or-no switch. They're not. Each warning points to a different question, and the right response depends on which one you're looking at.
| Signal | What it tells you | What it doesn't tell you | Action before installing |
|---|---|---|---|
| Full Provenance | Every file has an attestation tied to a publisher or build | Whether the source code is safe | Spot-check the attestation's source commit |
| No Provenance | Origin can't be cryptographically verified | That the release is malicious | Weigh maintainer history and repo activity |
| Incomplete Provenance | Attestations exist for only some files | Which files are the problem | Check release notes and the issue tracker |
| Change of Provenance | Build source differs from the previous release | Whether the change was an attack | Confirm an announced migration |
| Loss of Provenance | A previously attested project stopped attesting | Why the change happened | Verify with maintainers before pinning |
Redesigned Pages, Release Files, and Release History
The rest of the interface supports the Security tab. Understanding it helps you read signals faster.
On the project detail page, provenance warnings now sit at the top, next to banners for yanked releases, archived projects, and pre-releases. Quarantine is the exception. If a project or release is quarantined, only the quarantine banner appears, because it overrides everything else. When a release has full provenance or warnings, its state shows in the sidebar and links to the Security tab.
The metadata sidebar has also been reordered. Information now sorts by how useful it is, not by how it was verified. Labels read either "PyPI data" or "Data verified by PyPI." The old layout grouped data by verification status, which made practical details harder to find. The new labels matter, though. "Data verified by PyPI" comes from PyPI's own checks, while other fields still reflect what the maintainer supplied.
The release files tab is now searchable and filterable, which helps on projects with hundreds of files. Each file shows its own provenance state. Late files carry an orange warning icon. A file is marked late when it was uploaded more than 14 days after the release's initial timestamp. These warnings only apply to releases before July 2026, when PyPI introduced a policy to reject new files arriving after 14 days. A late file on an old release is worth noticing. Under the newer policy, PyPI rejects it outright.
The release history tab adds file count, provenance state, and release status: quarantined, yanked, archived, or pre-release. One detail many developers miss: a yanked release is hidden from default resolution, but it still installs if you pin it exactly. Seeing "yanked" next to a version you're already pinned to is a reason to check why.
Why "No Provenance" Isn't Automatically a Red Flag
Here's the counter-intuitive finding. The lazy advice goes like this: skip any package that lacks attestations. That rule sounds rigorous, but it misreads what the state means.
PyPI's own guidance says "no provenance" means the origin can't be cryptographically verified. It doesn't say the file is malicious. Many older releases predate Trusted Publishing. Many maintainers simply haven't switched over. If you applied a blanket rule, you'd reject large parts of the ecosystem that have worked safely for years.
A better comparison looks like this. Imagine two dependencies, both unattested. The first is a small utility, maintained by the same person for seven years, linked to an active repository with responsive issue threads. The second is a new package from an account created last week, with no linked repository and a first release that appeared yesterday. Both lack provenance. They don't carry the same risk.
When provenance is missing, lean on the surrounding signals PyPI's guidance points to: maintainer history, release patterns, and repository activity. Ask whether release cadence looks normal, whether the repository and the package metadata agree, and whether the maintainer responds to problems.
There's a real trade-off, though. Teams that block all unattested installs in CI get stronger guarantees on new code, but they'll run into friction with older, critical dependencies that will never gain attestations. That's a defensible policy for high-stakes systems, as long as you've decided it deliberately.
Checking PyPI Package Provenance Before You Install
Here's a workflow you can run in about two minutes per dependency:
- Open the project page and read the banners at the top. A quarantine, yank, or archive notice changes everything else.
- Open the Security tab and note the release's provenance state. Full, none, or a specific warning.
- For full provenance, check the attestation metadata. Confirm the source repository and commit match the project you think you're installing.
- For any warning, read the release notes and the issue tracker. Look for an announced migration or a documented build change.
- Open the release history tab to see whether the provenance state changed between versions. A shift from full to none is the pattern worth investigating most.
This process won't catch every compromise. It will catch the most common signs of a publishing pipeline that changed without explanation, which is the failure mode attestations were designed to expose.
Frequently Asked Questions
What is PyPI package provenance?
PyPI package provenance is a verifiable record of where a release file came from, meaning the publishing identity and the build source. It's stored as attestations. PyPI calculates a release's provenance state from them, and the Security tab displays that state. Full provenance means every file has an attestation.
How do I check if a PyPI package has provenance?
Open the project's page on PyPI and go to the Security tab. The release's provenance state appears there, along with per-file attestation metadata. You can also see a provenance state for each file in the release files tab. If a release has full provenance or warnings, the sidebar links you straight to the Security tab.
Why does a PyPI package show no provenance?
Usually because none of the release's files carry attestations. Older releases often predate Trusted Publishing, and some maintainers still upload with API tokens. "No provenance" means the origin can't be verified cryptographically. It doesn't mean the package is malicious, so check maintainer history and repository activity before deciding.
When should I worry about a PyPI provenance warning?
Worry most about Change of Provenance and Loss of Provenance on a project you already depend on. A change in the source repository or workflow can signal a compromised pipeline, and a project that stops attesting may have changed its publishing process. Check release notes and official channels before installing, and don't pin the new version until you've confirmed the change.
Pick one dependency in your requirements file this week, open its Security tab, and write down its provenance state. Then pass this along to a teammate who's pinning dependencies without checking where the files came from.