a128a60982
* docs: Add dependency cooldown docs * fix: Remove unnecessary params * Update docs/dependency-cooldown.md Co-authored-by: Sahil Bansal <bansalsahil315@gmail.com> Signed-off-by: Abhisek Datta <abhisek.datta@gmail.com> * fix: Cooldown guarantees --------- Signed-off-by: Abhisek Datta <abhisek.datta@gmail.com> Co-authored-by: Sahil Bansal <bansalsahil315@gmail.com>
1.5 KiB
Dependency Cooldown
Dependency cooldown filters package versions published within a configurable time window out of registry metadata responses during version resolution. This reduces exposure to supply chain attacks by ensuring the package manager normally only resolves versions that have been available for a minimum number of days.
How It Works
When cooldown is enabled, PMG intercepts package metadata responses from the registry and strips versions published within the cooldown window. If the requested version range allows an older eligible release, the resolver falls back to it automatically. If no eligible version satisfies the request, the install fails.
Cooldown is enforced through metadata filtering and does not apply to direct tarball installs or workflows that already have a resolved tarball URL (e.g., lockfile or cache scenarios).
Configuration
Dependency cooldown is configured in config.yml. See config template for the full schema. If you don't have a config.yml file, create one by running pmg setup install.
dependency_cooldown:
enabled: true
days: 5
CLI Override
Use --skip-dependency-cooldown to disable cooldown enforcement for a single invocation without changing the config file:
pmg --skip-dependency-cooldown npm install express
Requirements
Dependency cooldown requires proxy mode to be enabled. It is currently supported for npm packages.