# How to read PyPI security signals before installing an AI or ML dependency

> PyPI's redesigned project pages now show per-file provenance and four kinds of provenance warning, aimed at catching releases that did not come from a project's maintainers rather than projects that were malicious from the start.

- Published: 2026-11-15
- By: Samir Sengupta (https://www.samcodeman.com/about)
- Canonical: https://www.samcodeman.com/writing/pypi-security-signals-vetting-ai-ml-dependencies
- How this was made: Drafted with Claude, Anthropic's model from 1 cited source, then checked against it in a second editing pass. Editorial policy: https://www.samcodeman.com/editorial-policy

## The short version

- PyPI now computes a provenance state for every release by checking whether each release file has an attestation. It shows that state in a new security tab, in the sidebar and in the release history.
- Full provenance means 100% of release files are attested. No provenance does not mean a release is malicious; it means the file's origin cannot be cryptographically verified.
- The four provenance warnings are incomplete, inconsistent, change of and loss of provenance. PyPI built them to flag files that may not have come from the maintainers, for example after an account or workflow takeover.
- Commenters on Hacker News point out that Trusted Publishing is limited to a small set of publisher providers. Missing provenance on an independently built package may reflect that limit rather than tampering.

PyPI's redesigned project pages, announced as live in a PyPI blog post published November 14, 2026, add a dedicated security tab that shows each release's provenance state and per-file attestations. They also add four provenance warnings displayed at the top of the project page. A release has full provenance only when 100% of its files carry an attestation; typically a release is either in that state or has no provenance at all. These PyPI security signals tell you whether a release file can be cryptographically traced to a Trusted Publisher or to a specific source commit and build, and whether that trail has changed from earlier releases. For engineers pulling AI and ML packages into production, PyPI's stated purpose for the warnings is spotting files that may not have come from a project's maintainers.

PyPI says the ecosystem's growth has made it an increasingly attractive target for malicious actors. Digital attestations, introduced in 2024, provide a verifiable record of where a release file came from. PyPI acknowledges that its interface did little to communicate their meaning, importance or limitations. The redesign was funded by the Open Source Security Foundation, implemented by Kabu Creative, and applies the recommendations in the OpenSSF Attestations Style Guide.

## What PyPI security signals the redesign adds

The visible changes are a new security tab, provenance warnings, a reordered metadata sidebar, and reworked release files and release history tabs. The security tab is where per-file attestations live. You can review attestation metadata in the UI or follow the transparency log link for more detail. The release history tab now lists file count, provenance state and release status for each release, where status can be quarantined, yanked, archived or pre-release.

Sidebar metadata is now ordered by utility and labeled either "PyPI data" or "Data verified by PyPI". The old design grouped and ordered data by verification status. The post does not list which fields fall under each label. When a release has full provenance or a provenance warning, the sidebar also shows its provenance state and links to the security tab.

## Full provenance requires 100% of files attested

PyPI calculates a release's provenance state by checking whether each release file has an attestation, and says a release will typically be in one of two states. Full provenance means 100% of the release files carry one or both of the supported attestation types. A PyPI Publish attestation confirms the file was published by a PyPI Trusted Publisher. A SLSA Build Provenance attestation links the file back to its exact source commit, build platform and instructions.

No provenance means no file in the release has an attestation. PyPI says this is typical for older releases and for projects that have not configured Trusted Publishing. It does not necessarily mean the release is malicious; it means the file's origin cannot be cryptographically verified. For those packages, PyPI tells users to rely on surrounding trust signals such as maintainer history, release patterns and repository activity. One Hacker News commenter offered examples: dlt shows no provenance, while datasette shows provenance on its files.

## Four provenance warnings and what to check for each

PyPI surfaces a prominent warning when provenance metadata looks unusual or conflicts with a project's history. The stated purpose is to help identify when a file may not have come from the project's maintainers, for example if an attacker has taken over an account or a publishing workflow. PyPI also says many warnings have legitimate explanations, but each one is worth checking before you install.

- Incomplete provenance: some files are attested and others are not, for example wheels published via Trusted Publishing but the source tarball uploaded with an API token. PyPI says to exercise caution, check release notes for build issues, or ask in the project's issue tracker before installing.
- Inconsistent provenance: files in the same release come from different build systems or source repositories. Check the attestation metadata to confirm all files came from sources controlled by the maintainers.
- Change of provenance: files come from a different repository or workflow than a previous release. This is often legitimate, such as an organization name change or repository migration, but it can also indicate a compromised pipeline or account takeover. Confirm through release notes or official channels that a migration was planned.
- Loss of provenance: a project that previously published with attestations now uploads without them. Check whether the maintainers deliberately switched back to API tokens or changed their publishing configuration so it no longer generates attestations.

> If this is unexpected, treat the release with skepticism until verified.
>
> - PyPI blog, on loss of provenance

## Quarantine banners and 14-day late file warnings

Provenance warnings now sit at the top of the project page alongside status banners for yanked releases, archived projects and pre-releases. If a project or release is quarantined, only the quarantine banner is shown, because it takes precedence over all other warnings and banners. The post does not explain what quarantine means for installation. Because it overrides every other signal, treating it as a stop condition is the conservative reading.

The release files tab adds search and filtering over long file lists, a per-file provenance state, and an orange warning icon for late files. A late file is one 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 to reject new files after 14 days. If you pin an older release, a late file in that release is worth checking before you install it.

## Why missing provenance is not proof of tampering

Commenters on Hacker News questioned what these signals prove. One noted that the warnings detect formerly benign projects whose PyPI entries were hijacked, not projects that were malicious from the start. That is consistent with PyPI's own framing of the warnings around account and workflow takeover. PyPI describes provenance as a record of where a file came from. The post makes no claim that it says anything about whether the code is safe.

One commenter asked whether the only Trusted Publisher providers are for-profit US companies, and others agreed or made the same point. That commenter builds releases on their own hardware using a pypa/manylinux image and asked whether they can provide attestation without a third-party service. Another said there is no way to attach their own public key to a PyPI account and sign uploads so the signature counts as an attestation. A commenter writing about PyPI's maintainers and admins said more publisher providers are wanted, and that support for Codeberg is being discussed in warehouse issue 19786. That commenter said new providers must show strong key management and rotation, because they effectively become the PyPI credential broker for projects that use them. The commenter added that one open issue is that Codeberg's server currently wants to store OIDC private keys on disk.

Taken together, no provenance on a package from an independent maintainer says little on its own, and PyPI says as much. Loss of provenance on a package that used to have it carries PyPI's explicit advice to treat the release with skepticism until verified. Another commenter argued that provenance attestation serves compliance more than real security, and the sources do not settle that debate. Two of the four warnings, change and loss of provenance, compare a release with earlier ones. They are therefore most informative for dependencies with a history of attested releases.

One commenter also raised an operational gap. If any files in a package are published with attestations and others are not, PyPI shows prominent warnings. The commenter said PyPI does not email maintainers when a non-attested file is uploaded. The PyPI blog post does not mention maintainer notifications. The same commenter described adopting attestations as a permanent switch, and a reply disputed that, linking to a discuss.python.org thread.

## A vetting order for AI and ML packages

PyPI has extended its package security guide to cover assessing source code security, checking provenance, verifying package integrity, protecting yourself from common attacks and reporting security issues. Combined with the new page elements, the signals suggest a short order of checks before you add or bump an AI or ML dependency.

1. Check the top of the project page for a quarantine, yanked or archived banner, and treat quarantine as a stop.
2. Read any provenance warning and match it to PyPI's guidance: release notes or the issue tracker for incomplete provenance, attestation metadata for inconsistent provenance, and official channels for change or loss of provenance.
3. Open the security tab and confirm the attested source repository and workflow are the ones the project documents. Use the transparency log link if anything looks off.
4. Compare the provenance state in the release history tab with earlier versions you already run, since change and loss of provenance are defined relative to earlier releases.
5. For packages with no provenance, fall back to maintainer history, release patterns and repository activity, and note which sidebar fields are labeled "Data verified by PyPI".
6. On pinned releases from before July 2026, check the release files tab for late files marked with the orange icon.

The sources do not describe an API or command-line way to read provenance states or warnings, so this announcement does not cover automating these checks in CI. PyPI says the security tab gives it a dedicated home for future attestation types and security notices. It has also published a case study in the OpenSSF Attestations Style Guide describing the design patterns and warnings from this project.

## Questions this raises

### Does a PyPI release with no provenance mean it is malicious?

No. PyPI says no provenance is typical for older releases and for projects that have not configured Trusted Publishing. It only means the file's origin cannot be cryptographically verified, so users should rely on signals such as maintainer history, release patterns and repository activity.

### What should I check when PyPI shows a change of provenance warning?

A change of provenance means files come from a different repository or workflow than a previous release. This is often legitimate, such as an organization rename or repository migration, but it can also indicate a compromised pipeline or account takeover. Confirm through release notes or official channels that the migration was planned.

### Do PyPI provenance warnings catch packages that were malicious from the start?

No. PyPI frames the warnings around spotting files that may not have come from a project's maintainers, such as after an account or workflow takeover. Provenance records where a file came from, and PyPI makes no claim that it shows whether the code is safe.

## Key facts

- PyPI's blog post of November 14, 2026 announced redesigned project pages with a new security tab showing per-file attestations.
- A release has full provenance only when 100% of its files carry a PyPI Publish or SLSA Build Provenance attestation.
- PyPI shows four provenance warnings: incomplete, inconsistent, change of provenance and loss of provenance.
- Late files, uploaded more than 14 days after the initial release, are flagged only on releases from before July 2026, when PyPI began rejecting them.
- Digital attestations were introduced in 2024. The redesign was funded by OpenSSF and implemented by Kabu Creative.

## Sources

1. [PyPI's redesigned project pages with clearer security signals are now live](https://blog.pypi.org/posts/2026-11-06-ui-updates-complete/) - blog.pypi.org

Discussion read (practitioners' reactions, not a source): https://news.ycombinator.com/item?id=50497892
