PyPI Adds Security Tab to Project Pages Showing Provenance, Attestations and Supply Chain Warnings
The Python Package Index (PyPI) redesigned its project detail pages and added a Security tab. The tab shows provenance status and digital attestations for each release. It gives developers a way to check where a package came from before they install it. It is a defensive feature, not a vulnerability or an incident. The article cites no CVEs, threat actors or exploitation.
Detalhes técnicos
- A full provenance badge appears when every file in a release carries a valid attestation. Releases without verified signatures show a missing-provenance status.
- The attestations combine Trusted Publisher records with SLSA build provenance. SLSA ties artifacts to source commits, build platforms and build steps.
- There are four warning categories:
- Incomplete: only some files are attested.
- Inconsistent: files come from different build systems or repositories.
- Changed: a different repository or workflow than earlier versions was used.
- Lost: a previously attested project publishes unsigned files.
- The files view now has search, filtering and per-file provenance indicators. The version history shows file counts, provenance badges and yanked or quarantined states.
- For releases before July 2026, PyPI shows an orange warning when files were uploaded more than 14 days late. The article says a July 2026 policy now blocks uploads made 14 days after the initial release.
- Limits: legitimate repository migrations or pipeline changes can trigger alerts. Provenance only authenticates the publishing origin and build environment. Developers should still review maintainer history and project activity.
Remediação
No remediation is needed. Developers can use the Security tab and its warnings when they evaluate dependencies. This record is based on the article alone, because no web research was done.
Linha do tempo
-
PyPI Adds Security Tab to Project Pages Showing Provenance, Attestations and Supply Chain Warnings
ler a análise desta fonte ocultar
The Python Package Index (PyPI) redesigned its project detail pages and added a Security tab. The tab shows provenance status and digital attestations for each release. It gives developers a way to check where a package came from before they install it. It is a defensive feature, not a vulnerability or an incident. The article cites no CVEs, threat actors or exploitation.
Technical Details
- A full provenance badge appears when every file in a release carries a valid attestation. Releases without verified signatures show a missing-provenance status.
- The attestations combine Trusted Publisher records with SLSA build provenance. SLSA ties artifacts to source commits, build platforms and build steps.
- There are four warning categories:
- Incomplete: only some files are attested.
- Inconsistent: files come from different build systems or repositories.
- Changed: a different repository or workflow than earlier versions was used.
- Lost: a previously attested project publishes unsigned files.
- The files view now has search, filtering and per-file provenance indicators. The version history shows file counts, provenance badges and yanked or quarantined states.
- For releases before July 2026, PyPI shows an orange warning when files were uploaded more than 14 days late. The article says a July 2026 policy now blocks uploads made 14 days after the initial release.
- Limits: legitimate repository migrations or pipeline changes can trigger alerts. Provenance only authenticates the publishing origin and build environment. Developers should still review maintainer history and project activity.
Remediation
No remediation is needed. Developers can use the Security tab and its warnings when they evaluate dependencies. This record is based on the article alone, because no web research was done.