npm · Snapshot 2026-10-26
@typescript-eslint/eslint-plugin release history
What happened to stable releases over the snapshot’s last 12 months.
- Releases in 12 months
- 46
- Pulled
- 0
- Fixed within 72 hours
- 0
- Share pulled or fixed
- 0.0%
- Normal release cadence
- 7 days
Pulled and fixed counts can overlap. Latest stable release: 8.72.0 · .
Recent pulled or quickly fixed versions
No pulled or quickly fixed releases recorded in this snapshot.
A practical setting
Give a new release three days.
In this snapshot, a 3-day cooldown would have waited past the replacement patch for 0 releases of @typescript-eslint/eslint-plugin 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: 3Renovate
{
"packageRules": [
{
"matchDatasources": [
"npm"
],
"matchPackageNames": [
"@typescript-eslint/eslint-plugin"
],
"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