PyPI makes package provenance changes easier to inspect
PyPI’s redesigned project pages add a Security tab showing where release files came from and whether their attestations are complete or consistent. Warnings highlight missing attestations, mixed origins and changes from earlier releases. These are investigation signals: a legitimate build migration can trigger a warning, while complete provenance identifies origins rather than proving that code is safe.
Python Package Index · Nov 6, 2026
Why it matters
Dependency review becomes more useful when it can compare a release’s publishing history instead of relying only on a package name.
More context
This November 6 update is an older discovery. Open a project’s Security tab, inspect per-file attestations and compare a warning with maintainer release notes. Publishing attestations identify a trusted publishing workflow; supported build-provenance records can connect a file to its source commit and build platform.
Keep in mind
Live interface update, not a malware scanner or safety certification. No provenance can be normal for older releases or projects without attestation-enabled publishing. Metadata needs interpretation alongside code, maintainer history and release context.
Original read