← All dependency release histories

npm · Snapshot 2026-10-26

next release history

What happened to stable releases over the snapshot’s last 12 months.

Releases in 12 months
88
Pulled
22
Fixed within 72 hours
10
Share pulled or fixed
26.1%
Normal release cadence
3.7 days

Pulled and fixed counts can overlap. Latest stable release: 16.4.3 · .

Recent pulled or quickly fixed versions

  • 16.2.8
  • 15.0.6
  • 15.1.10
  • 15.2.7
  • 14.2.34

An example maintainer reason for a pulled release

This version has a security vulnerability. Please upgrade to a patched version. See https:

Registry text, truncated to 90 characters by the source dataset. This package-level example is not mapped to a specific version above.

A practical setting

Give a new release three days.

In this snapshot, a 3-day cooldown would have waited past the replacement patch for 10 releases of next fixed within 72 hours. This describes release timing; it does not establish why a patch was published or guarantee that an update will hold up.

Merge these settings into your existing configuration and adjust the manifest directory. Dependabot applies this to version updates; security updates are handled separately. The Dependabot example covers the ecosystem; the Renovate example targets this package.

Dependabot

version: 2
updates:
  - package-ecosystem: "npm"
    directory: "/"
    schedule:
      interval: "daily"
    cooldown:
      default-days: 3

Renovate

{
  "packageRules": [
    {
      "matchDatasources": [
        "npm"
      ],
      "matchPackageNames": [
        "next"
      ],
      "minimumReleaseAge": "3 days"
    }
  ]
}

Dependabot cooldown reference · Renovate release age reference

These are outcomes, not predictions. A quick patch is a timing signal, not proof that a release was defective. This table does not detect compromised or malicious releases; for security, use a dedicated supply-chain scanner.

Methodology and column definitions →

See this for your own code.

Rework Risk finds the merged pull requests in your repo that later needed corrective work, dependency bumps included.

Get a rework backtest on your repo