PyPI Implements 14-Day Upload Window to Prevent Supply Chain Poisoning
Score
80PyPI 的这一安全规则此前未被广泛报道，对社区有较高的信息增量。
引用官方博客原始声明，数据准确，逻辑清晰，表述规范。
对于所有 PyPI 项目维护者及依赖 Python 的团队，直接影响发布流程和安全策略。
文章发布日期为2026年7月23日，与规则生效日一致，时效性极高。
来源为 PyPI 官方博客，作者 Seth Larson 为 PyPI 安全团队成员，可信度高。
Base 88.5 × T2 Source weight ×0.9 = 80
Curation line 70Selected
Why selected
The rule is simple yet effective, directly closing a long-standing security gap without introducing complexity, and highly operational.
AI commentary
「This is a critical message for the Python ecosystem. If you maintain any PyPI project, check your release workflow immediately — the 14-day window means you can no longer patch or overwrite files on old releases; you must publish a new version. For security teams, this is a best practice in supply chain security worth emulating by other package managers.」
Quick overview
The Python Package Index (PyPI) now rejects file uploads to releases older than 14 days. This restriction prevents poisoning of long-stable releases via compromised publishing tokens or workflows. No known exploitation has occurred, but attackers were previously unaware of the possibility. The measure strengthens Python software supply chain security.
- PyPI prohibits uploading new files to releases older than 14 days.
- The measure prevents poisoning of long-stable releases due to credential leaks.
- No known exploitation has occurred, but the technical possibility existed.
- Enhances PyPI's defense against supply chain attacks.
Full text
Showing the source text; the full translation is being generated.
The Python Package Index (PyPI) now rejects new files being uploaded to releases that are older than 14 days. This restriction was put in place to prevent old and long-stable releases from being poisoned in case publishing tokens or workflows of PyPI projects were compromised. As far as we are aware this has not yet been abused, but there is no technical reason beyond that attackers weren't aware it was possible.
— Seth Larson, PyPI blog
Tags: packaging, python, supply-chain, pypi, seth-michael-larson
Related items
89
FeaturedOpenAI Research: AI Is Redefining Job Boundaries
OpenAI研究：AI正在重新定义工作边界
If you care about the real impact of AI on work, this research is a must-read. Instead of theory, it uses data to show how ChatGPT users expand their task scope, offering direct insights for HR, managers, and every professional looking to upgrade their skills.
87
FeaturedOpenAI CFO Shares Five Lessons for Building an AI-Native Finance Function
OpenAI CFO 分享构建 AI 原生财务职能的五大经验
As an editor, I find this article uniquely valuable because it comes from a finance chief at an AI leader, not an external consultancy, making it highly practical. I recommend it to finance digitalization leads, CFOs, and anyone interested in AI-driven transformation.
87
FeaturedScientific Computing in the Age of Agentic AI: OpenAI Releases New Field Report
智能体AI时代下的科学计算：OpenAI发布新领域报告
This report is one of the most practical analyses in the current AI agent wave, especially suitable for practitioners in computational biology and drug discovery. It answers the key question 'What can AI agents do besides writing code?' and directly demonstrates productivity gains in complex scientific computing.
87
FeaturedReal World VoiceEQ: Measuring the Human Quality of Voice AI
Real World VoiceEQ：量化语音AI的人类自然度
What's noteworthy is that this benchmark truly focuses on the soft metric of 'human-likeness', not traditional speech recognition rate or MOS scores. For teams working on speech synthesis, voice cloning, or voice interaction, this is a highly practical reference tool that quickly identifies model deficiencies in emotion, prosody, etc. However, language support is currently limited; looking forward to future expansion.
85
FeaturedOpenAI Introduces AI Age Scorecard: A New Way to Measure ROI
OpenAI 推出AI时代记分卡：衡量投资回报的新方法
This blog post hits a sore point in the current AI industry: how to quantify input-output. For enterprise decision-makers deploying or planning large-scale AI, it helps avoid herd mentality. My personal advice: try defining 'useful work' based on your own business scenario, and avoid designing metrics that are merely formality.
85
FeaturedHow to Manage AI Investments in the Agentic Era: Focus on Useful Work per Dollar and High-Value Workflows
代理时代如何管理AI投资：聚焦每美元有用功与高价值工作流
This article is especially important for enterprises scaling AI agents. It reminds us that focusing solely on falling API prices is a trap; what really matters is the return per unit of work. I recommend CTOs and CFOs read it together and establish quantitative evaluation mechanisms internally.
85
FeaturedDesigning Organisations That Can Keep Up With AI: Organisational Latency as the Biggest Barrier
设计能跟上AI的组织：组织延迟成为最大障碍
What makes this article truly worth following is that it raises a neglected bottleneck: no matter how strong the technology is, if the organisation can't keep up, it's useless. For CTOs, CIOs, and transformation leaders, this is a more important framework than tech selection.
84
FeaturedRuff v0.16.0 Released: Default Rules Jump from 59 to 413, CI Pipelines Need Attention
Ruff v0.16.0 发布：默认规则从59条激增至413条，CI工作流需关注
For Python developers, this is an unmissable update signal. The significant increase in Ruff's default rules means we can no longer ignore potential issues in our code, and AI fix tools can lower the upgrade cost. Notably, Astral (OpenAI) is deeply integrating AI coding capabilities with static analysis tools, which may become the norm in future engineering practices.