PyPI has launched a Security tab and publishing-origin warnings on its package pages. Developers can see whether release files came through an expected publishing workflow and investigate a change before installing them.

Nicole Harris’s November 6 announcement describes the completed redesign. Harris is a PyPI design contributor; OpenSSF funded the work, and Kabu Creative implemented it. This is a first-party account of the interface and its intended use.

Evidence status: a released defensive feature, not a newly disclosed compromise. The announcement provides no measured reduction in attacks. Its value is making existing release evidence easier to inspect.

File origin is a separate question from code safety

Provenance means where a release file came from. PyPI displays it through attestations, signed statements about publishing or building a file. Its user documentation distinguishes two supported types:

  • PyPI Publish attestations confirm upload through a configured Trusted Publisher identity, such as a particular GitHub Actions workflow. PyPI checks that identity against the maintainer’s configuration.
  • SLSA Build Provenance attestations describe how a build platform produced a file, including its source and build information where available.

Full provenance means every file in that release has an attestation of a supported type. It does not mean every file carries both types. Read the actual statement before assuming it proves a specific source commit or build process.

An attacker who controls the trusted repository or publishing workflow can still produce dangerous code. Conversely, an older release with no attestations may simply predate their adoption. PyPI’s documentation explicitly separates origin evidence from trust in the code and build environment.

Four warnings call for different checks

The redesigned pages surface these conditions:

Warning What changed What to check before installing
Incomplete provenance Some release files have attestations; others do not. Whether the specific wheel or source archive you need has the expected evidence. Check for a documented publishing problem.
Inconsistent provenance Files within one release come from different pipelines or repositories. Whether all those origins belong to the maintainers.
Change of provenance The repository or workflow differs from a previous release. An announced repository move or publishing migration through established project channels.
Loss of provenance A previously attested project now publishes files without attestations. Whether maintainers intentionally changed their upload process or disabled attestation generation.

These are prompts to investigate, not automatic findings of account takeover. A legitimate migration can change origin metadata. An unexplained change deserves a pause before the dependency enters your build.

Review the artifact your deployment actually selects

Start with the release’s Security tab, then inspect the relevant file and its publishing identity. Compare it with the project’s expected repository, workflow and release history. A healthy-looking file elsewhere in the same release does not establish the origin of yours.

The release-files tab also marks files uploaded more than 14 days after a release began. Those warnings concern older releases, before PyPI’s July 2026 policy began rejecting such late additions. They do not show that new releases can still accept arbitrarily late files.

Maintainers can adopt Trusted Publishing with a publisher that generates attestations. Users can verify statements through PyPI’s documented Integrity API and attestation-verification tooling.

The page redesign does not add native enforcement to common installers. At review time, PyPI’s documentation says verification is not built into pip or uv. A warning visible in a browser should not be assumed to stop an unattended installation.

Caveat: Attestations identify origin under their stated trust assumptions; they cannot certify that the original code or its build environment is safe.