PyPI's redesigned project pages with clearer security signals are now live
Points and comments are a snapshot, not live.
PyPI's redesign surfaces digital attestations and provenance warnings on package pages.
PyPI completed a UI redesign focused on security signals. A new Security tab shows per-file digital attestations and calculates a release's provenance state (Full or No Provenance). Four warning types (Incomplete, Inconsistent, Change, Loss of Provenance) appear when attestation metadata is unusual. The project detail page, release files tab, and release history tab were also updated. The work was funded by the OpenSSF and implemented by Kabu Creative, with extended user documentation on package security.
What commenters are saying
Many commenters criticize attestation as a compliance tool favoring large CI providers. A top comment notes that only for-profit US companies (GitHub, GitLab, Google) are supported as trusted publishers, excluding local builds or independent forges like Codeberg. Others argue attestations are about authenticated auditing, not inherent security. A user reports that once a project uses attestations, all future files must use them or PyPI shows warnings, with no email notification to maintainers about the non-compliant upload.