PyPI's redesigned project pages with clearer security signals are now live

PyPI has rolled out redesigned project pages that surface software provenance and digital attestations, tying “trusted” status to builds produced via certain CI providers using OIDC-based workflows. Commenters welcome stronger supply-chain signals in theory but argue the current model privileges large for-profit forges (e.g., GitHub, GitLab), excludes maintainers who build and sign locally, and risks being misinterpreted as a security guarantee rather than a narrow statement about who built and uploaded a package. Several also question the practicality and clarity of the new system, calling for alternative attestation mechanisms (such as email- or key-based options), support for smaller or self-hosted platforms, and better documentation for both publishers and end users.

UI Changes and Early Bugs

  • New project pages highlight provenance and security signals per file.
  • Example screenshots show icons and indicators for source dists vs wheels; at least one mobile layout bug is reported.
  • Some argue “nobody looks at these pages,” others say that’s exaggerated.

Attestations and Trusted Publishing

  • Attestations show who/what built and published a file (typically CI on a major forge), not whether the package is “safe” or non‑malicious.
  • They mainly help detect account or project hijacks and unexpected publishing paths.
  • Mixing attested and unattested files in a project can trigger prominent warnings; this behavior has been controversial and partially clarified.

Centralization and Big-Tech Dependence

  • Strong concern that “trusted publisher” status currently depends on a small set of large, for‑profit US platforms (GitHub, GitLab, Google, etc.).
  • Critics see this as de‑facto lock‑in and anti‑decentralization; supporters call it pragmatic given limited PyPI resources and the need for strong key management from providers.

Alternatives: Local Builds, PGP, and New Mechanisms

  • Many want a way to attach their own public key to PyPI and sign uploads locally (possibly via hardware tokens), instead of going through a forge.
  • PyPI previously supported PGP signatures but removed them due to very low adoption and many insecure/invalid signatures.
  • Maintainers argue “greenfield” designs should avoid long‑lived user keys and lean on short‑lived, OIDC‑based identities; critics say offering a power‑user key option harms no one.
  • Email-based attestations and support for more forges (e.g., Codeberg, self‑hosted OIDC) are discussed but not yet implemented; open issues exist.

Security Value vs. Compliance and Threat Model

  • Skeptics see provenance mainly as compliance signaling: “built on Microsoft/Google” doesn’t inherently make code safer.
  • Others stress the value of cryptographic, time‑bound audit trails and authenticated state over time, even if they don’t prevent malicious maintainers.
  • Some advocate reproducible builds and multi‑party verification as more robust, but maintainers note Python packaging is far from reproducible and enforcing this would be disruptive.

Documentation, Terminology, and User Perception

  • Several commenters find the terminology (“trusted/authorized publisher,” “build,” “project”) confusing and fear users will misread “no provenance” as “dangerous.”
  • There is worry that maintainers who build locally or avoid big forges will be unfairly stigmatized by UI labels and warnings.