Back to Home
Socket Blog··Papers & Tech

Composer 2.11 Adds Dependency Cooldowns

中文摘要

Composer 2.11 引入了依赖冷却机制,允许开发者通过配置等待时间来延迟安装新包,以降低供应链攻击风险。

English Summary

Composer 2.11 introduces dependency cooldowns, allowing developers to delay new package versions via a configuration setting to mitigate supply chain attack risks.

Original Excerpt

Composer 2.11 has introduced dependency cooldowns, giving PHP developers a native way to delay newly published package versions before they become eligible for installation. The release arrives nearly a year after developers first requested the feature, bringing Composer into line with package managers that have already adopted minimum release age policies to reduce exposure to supply chain attacks. The new config.policy.cooldown setting allows developers to specify a waiting period in hours, days, or weeks. It is disabled by default and applies during dependency resolution, including composer update and composer require. Existing lockfile installations remain unaffected. The feature also supports organization-wide configuration through Private Packagist, which can enforce cooldowns regardless of the Composer version developers and CI systems are running. Preventing Cooldown Bypasses # The original GitHub issue opened in November 2025 and gained urgency following a series of high-profile supply chain compromises. An initial implementation was submitted in December, but the feature missed Composer 2.10 as the maintainers worked through how to enforce cooldowns reliably. In May, afte…