PyPI has completed a redesign of its project pages to make package security information easier to find and understand. The central change is a Security tab that shows attestations for individual release files and summarizes each release’s provenance: whether its origin can be cryptographically verified. Full provenance means every file has at least one supported attestation: a PyPI Publish attestation confirming publication through a Trusted Publisher, or SLSA build provenance linking a file to its source commit, build platform, and instructions. No provenance means no files have attestations; this is common for older releases and does not by itself mean a package is malicious, but its origin cannot be verified cryptographically.
The interface also highlights four warning states: incomplete provenance when only some files are attested; inconsistent provenance when files come from different build systems or repositories; a change in provenance between releases; and loss of provenance when a project stops publishing attestations. These can have legitimate causes, but users are advised to check release notes, official channels, or project maintainers before installing. Provenance warnings now appear prominently, and the sidebar links to security details. Redesigned Release files and Release history tabs add filtering, file-level provenance, release statuses, and file counts; late uploads are flagged for releases before a July 2026 policy began rejecting files added more than 14 days after release. Updated documentation offers further guidance on assessing package security.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.