PyPI now rejects new files after 14 days

Python Software Foundation security developer-in-residence SethLarson has announcedthat the Python Package Index (PyPI) will now reject new files thatare uploaded to releases older than 14 days. The restriction is toprevent the poisoning of old releases if publishing tokens orworkflows of PyPI projects are compromised.

The discussionof this behavior began during PEP 740 (Digital Attestations) back in January2024. The discussion was restartedin March 2026 after the popular packages LiteLLMand Telnyx were compromised. These packages were compromised due to a "mutablereference" in these projects' usage of the Trivy GitHub Action.

Originally the discussion stalled due to some projects depending on this behaviorto add support for new Python versions to already-published releases. To quantify howdisruptive this change would be to existing workflows, the PyPI database was queriedfor projectsthat have published new files to old releases (bucketed by number of days sincethe release). Later, specifically cp314 wheels were queried for the top15,000 packages, revealing that only56 projects of 15,000 had published a 3.14-compatible wheel more than 14 daysafter a release was available.

LWN covered the LiteLLM compromisein March.