SecurityOnlineDo Son
PyPI adds provenance warnings to help users spot risky packages
The Python Package Index (PyPI) has unveiled a redesigned project detail experience centred on provenance and supply chain warnings. The new PyPI Security Tab shows cryptographic attestations and provenance status for every release, with per-file provenance indicators, warning banners for anomalous files and a history view of version states. PyPI’s aim is to make package origins more transparent before dependencies are installed, strengthening protection against escalating software supply chain attacks.
The changes are described as combining PyPI Trusted Publisher records with SLSA build provenance metadata, allowing developers to inspect cryptographic metadata and transparency logs directly on a project page.
The update introduces four provenance warning categories to help developers spot suspicious releases: incomplete provenance (some files lack attestations), inconsistent provenance (files drawn from different build systems), changed provenance (artifacts built via a different workflow or repository), and lost provenance (previously attested projects publishing unsigned files).
Additionally, PyPI has refreshed the release files and version history views to improve visibility, with instant search, granular filtering and per-file provenance indicators. The article notes a special policy for older releases, with PyPI displaying an orange warning for files uploaded more than fourteen days after a release and, from July 2026, a strict ban on uploads fourteen days post-release.
The piece stresses that provenance verification authenticates publishing origins and build environments, while maintainer histories and project activity remain important factors in risk assessment. Claims are attributed to PyPI and linked official announcements, with caution advised for potential false positives in migrations or pipeline changes.