← Voltar ao feed
low

PyPI adds Security tab to project pages showing release attestations, provenance status and supply chain warnings

2 fonte(s) · 2 atualização(ões) · publicado 09/11/2026 10:23 · coletado há 1 dia

Matéria consolidada. Reúne 2 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 2 fontes trouxeram em 16/11/2026 12:03; os links antigos trazem para cá.

Fontes: securityonline.info ↗ helpnetsecurity.com ↗

The Python Package Index (PyPI) has redesigned its project detail pages and added a Security tab. The tab shows whether each release file carries a digital attestation, so developers can check where a package came from before installing it (helpnetsecurity.com, securityonline.info). A release has full provenance when every file is attested and no provenance when none is. Missing attestations are common for older releases and for projects that have not configured Trusted Publishing, and they do not by themselves mean a package is malicious (helpnetsecurity.com). This is a defensive feature, not a vulnerability or an incident. No CVEs, threat actors or exploitation are cited (securityonline.info). The sources were published on 2026-11-09 and 2026-11-16.

Detalhes técnicos

  • A PyPI Publish attestation identifies the Trusted Publisher that uploaded the file. A SLSA Build Provenance attestation links the file to its source commit, build platform and build instructions (helpnetsecurity.com, securityonline.info).
  • Users can review attestation details in the tab or open the linked transparency log (helpnetsecurity.com).
  • PyPI shows four warning categories (securityonline.info):
    • Incomplete: only some files in a release are attested.
    • Inconsistent: files in one release come from different repositories or build systems.
    • Changed: a different repository or workflow than in earlier versions was used.
    • Lost: a project that previously published attestations now publishes unsigned files.
  • Provenance warnings appear at the top of the redesigned project page, next to yanked, archived and pre-release notices. Quarantined projects or releases show only the quarantine banner (helpnetsecurity.com).
  • The Release Files tab has search, filtering and per-file provenance indicators (securityonline.info). It flags files uploaded more than 14 days after a release that predates PyPI's July 2026 policy change. Since that change, PyPI has refused late uploads (helpnetsecurity.com, securityonline.info).
  • The Release History tab shows file count, provenance status and release status (yanked or quarantined) for each version (helpnetsecurity.com, securityonline.info).
  • Limits: legitimate repository migrations or pipeline changes can trigger alerts. Provenance only authenticates the publishing origin and build environment, so developers should still review maintainer history and project activity (securityonline.info).

Remediação

No remediation is needed (securityonline.info). Developers can use the Security tab and its warnings when evaluating dependencies. The securityonline.info assessment is based on the article alone, with no additional web research.

Linha do tempo

  1. securityonline.info ↗ · pub. 16/11/2026 01:15 · coletado 16/11 02:00

    PyPI Adds Security Tab to Project Pages Showing Provenance, Attestations and Supply Chain Warnings

    ler a análise desta fonte

    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.

  2. helpnetsecurity.com ↗ · pub. 09/11/2026 10:23 · coletado 09/11 12:00 primeiro registro

    PyPI adds Security tab to show release file attestations and provenance status

    ler a análise desta fonte

    The Python Package Index (PyPI) has added a Security tab to project pages that shows whether each release file carries a digital attestation, so developers can check where a package came from before installing it. A release has full provenance when every file is attested and no provenance when none is. The article notes that missing attestations are common for older releases and for projects that have not configured Trusted Publishing, and that they do not by themselves mean a package is malicious. PyPI now warns when only some files in a release are attested, when files in one release come from different repositories or build systems, or when a project that previously published attestations stops doing so.

    Technical Details

    • A PyPI Publish attestation identifies the Trusted Publisher that uploaded the file.
    • A SLSA Build Provenance attestation links the file to its source commit, build platform and build instructions.
    • Users can review attestation details in the tab or open the linked transparency log.
    • The redesigned project page shows provenance warnings at the top, next to yanked, archived and pre-release notices. Quarantined projects or releases show only the quarantine banner.
    • The Release Files tab flags files uploaded more than 14 days after a release that predates PyPI's July 2026 policy change. Since that change, PyPI has refused late uploads.
    • The Release History tab shows file count, provenance status and release status for each version.