A cooldown is a built-in waiting period before an automated update, deployment, or other action is allowed to continue. In security tools, it adds delay on purpose so a fresh change is not trusted immediately just because it is new.
Cooldowns matter in cyber security because many attacks exploit speed. In a software supply chain, a malicious or compromised package can be most dangerous right after release, before defenders have time to inspect it. By waiting, automation gives analysts, package maintainers, and reputation systems time to spot broken or suspicious releases. Defenders use cooldowns in dependency update tools, release pipelines, and account protections to reduce the value of rapid abuse. The trade-off is slower delivery, so urgent security fixes are often exempted or handled on a faster path.