dependency-cooldown

Configures minimum release age cooldowns across package managers and update bots.

4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/staticaland/skills --skill dependency-cooldown-staticaland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-cooldown
Source: https://github.com/staticaland/skills/tree/main/plugins/dependencies/skills/dependency-cooldown
Command: npx skills add https://github.com/staticaland/skills --skill dependency-cooldown-staticaland

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Freshly published package versions are a common supply-chain attack vector, and this Skill sets up dependency cooldowns that hold back new releases for a configurable period so compromised versions are caught before reaching your project. ## Core Features & Use Cases - Resolution site inventory: Scans the repository for every package manager, lockfile, CI workflow, Dockerfile, and update bot that resolves dependencies, so no unprotected install path is missed. - Per-manager configuration: Applies the correct cooldown setting for npm, pnpm, Yarn, Bun, Deno, uv, pip, Poetry, PDM, pixi, Bundler, Hex, mise, pinact, Renovate, Dependabot, and more, with version gates and per-package bypasses. - Verification and conflict detection: Reads settings back through each tool, runs dry-run resolutions, and detects environment variables or shell wrappers that silently override committed config. - Use Case: After a supply-chain incident, ask the agent to add a 3-day cooldown to a polyglot repo; it finds the npm, uv, and Dependabot resolution sites, writes the committed config, and verifies each gate holds back fresh versions. ## Quick Start Set up a 3-day dependency cooldown across every package manager and update bot in this repository.

Frequently Asked Questions about dependency-cooldown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a dependency cooldown for npm and pip?▼

For npm 11.10.0+, set min-release-age in days in the project .npmrc. For pip 26.1+, set uploaded-prior-to as an ISO 8601 duration like P3D in pip.conf or the PIP_UPLOADED_PRIOR_TO environment variable.

What is a dependency cooldown or minimum release age?▼

A cooldown is a minimum release age that prevents package managers from resolving versions published less than N days ago. It gives researchers time to catch compromised releases before they reach your project.

Does Dependabot support cooldowns for security updates?▼

Dependabot supports cooldown configuration in dependabot.yml with default-days and per-semver-level settings, but it exempts security updates from cooldowns so CVE fix pull requests still arrive immediately.

Why is my cooldown config not working in CI?▼

A tool below the minimum supported version silently ignores the setting, and exported environment variables like UV_EXCLUDE_NEWER or npm_config_min_release_age can outrank the committed project file. Check tool versions and grep workflows for exported variables.

Which package managers have no native cooldown support?▼

Go, NuGet, Composer, Dart pub, Swift Package Manager, Maven, Gradle, and conda have no native cooldown. For these, lock exact versions and rely on an update bot cooldown or a registry-level proxy like Artifactory, Nexus, or Verdaccio.

What are the limitations of dependency cooldowns?▼

Cooldowns do not protect against typosquatting, long-term maintainer compromise, or vulnerabilities in versions already installed. Pair them with tools like npm audit, pip-audit, or Dependabot security alerts.