ESLint End of Life (EOL) Dates and End of Support (EOS) Dates
ESLint end of life (EOL) and end of support (EOS) dates: 9 ESLint versions have reached EOL, including ESLint 9 (EOL date: Aug 06, 2026) — no longer receiving security updates or patches. ESLint 10.14.0 is the current supported release. Also see Bazel lifecycle dates for related end-of-life information.
Currently Supported ESLint Releases - Active EOS/EOSL Support (1)
| Release | Eoes Provider | Released | Maintenance Support | Active Support | Extended Long Term Support | Latest |
|---|---|---|---|---|---|---|
| 10 | Tidelift | (9 months ago) | Active | Active | Active | 10.14.0 (1 week and 6 days ago) |
ESLint End of Life (EOL) Releases - No Longer Supported (9)
| Release | Eoes Provider | Released | Maintenance Support | Active Support | Extended Long Term Support | Latest |
|---|---|---|---|---|---|---|
| 9 | Tidelift | (2 years and 7 months ago) | (3 months ago) | (11 months ago) | Active | 9.39.5 (4 months ago) |
| 8 | HeroDevs | (5 years and 1 month ago) | (2 years and 1 month ago) | (2 years and 7 months ago) | Active | 8.57.1 (2 years and 1 month ago) |
| 7 | - | (6 years and 6 months ago) | (4 years and 7 months ago) | (5 years and 1 month ago) | Active | 7.32.0 (5 years and 3 months ago) |
| 6 | - | (7 years and 4 months ago) | (6 years ago) | (6 years and 6 months ago) | Active | 6.8.0 (6 years and 10 months ago) |
| 5 | - | (8 years and 4 months ago) | (6 years and 10 months ago) | (7 years and 4 months ago) | Active | 5.16.0 (7 years and 7 months ago) |
| 4 | - | (9 years and 5 months ago) | (7 years and 10 months ago) | (8 years and 4 months ago) | Active | 4.19.1 (8 years and 7 months ago) |
| 3 | - | (10 years and 4 months ago) | (8 years and 11 months ago) | (9 years and 5 months ago) | Active | 3.19.0 (9 years and 7 months ago) |
| 2 | - | (10 years and 9 months ago) | (9 years and 10 months ago) | (10 years and 4 months ago) | Active | 2.13.1 (10 years and 4 months ago) |
| 1 | - | (11 years and 3 months ago) | (10 years and 3 months ago) | (10 years and 9 months ago) | Active | 1.10.3 (10 years and 11 months ago) |
If you maintain a JavaScript project, ESLint end of life decides how long your linting keeps getting fixes. ESLint is a static code analysis tool, so developers rely on it, and on its plugins, staying supported. Here are the dates, the rules behind them and your options.
ESLint End of Life Dates for Every Major Version
| Release | Active support ended | Maintenance support ended | Latest |
|---|---|---|---|
| v10 | Still active | Not yet | 10.13.0 |
| v9 | 14 Nov 2025 | 6 Aug 2026 | 9.39.5 |
| v8 | 5 Apr 2024 | 5 Oct 2024 | 8.57.1 |
| v7 | 9 Oct 2021 | 9 Apr 2022 | 7.32.0 |
The project itself offers no long term support track; only paid vendors extend a retired line.
ESLint v8.x End of Life: October 5, 2024
The end of life for ESLint v8.x meant the team stopped making changes or shipping builds in the v8 line on October 5, 2024, so v8 has seen no further updates since. Since ESLint v8.x is end of life, any project on the last v8 build runs an unsupported version.
Why ESLint v9 Is Also Unsupported Now
The ESLint 9 line, first shipped as ESLint v9.0.0, left its supported window on 6 August 2026. If you use v9, plan your move to the latest version, v10.
How the ESLint Version Support Policy Defines EOL
The Technical Steering Committee adopted a formal version support policy to end the confusion around each major release.
Three Statuses from Current to End-of-Life
Every release line passes through three stages:
- Current: the team adds features and fixes, starting at prerelease.
- Maintenance: only critical bug fixes, security fixes and compatibility fixes arrive, with no backporting of other work.
- EOL: bug fixes and every other release stop.
A line stays in that stage until six months after general availability of its successor.
Why ESLint Keeps a Single Release Line
ESLint is an open-source project maintained by volunteers in their spare time, which is the reason the team gives for not running parallel lines. That is why each supported release window is short.
Risks of Running an Unsupported Version
An unsupported ESLint release still runs, but its dependencies keep aging while software around it moves on. Any vulnerability found after v8 or v9 retired, such as a new CVE, stays open, and no fixes ship for those lines. The practical risk grows quietly, because nothing breaks on the day support ends.
Security Patches and Compliance Exposure
Teams under regulated frameworks need security patches that someone is accountable for:
- Security audits can flag a retired ESLint package in your npm lockfile.
- Compliance reviews under SOC 2, HIPAA, FedRAMP or PCI may ask for supported dev tooling.
- A vendor SLA can answer that requirement.
HeroDevs Commercial Support and Upgrade Paths Beyond End-of-Life
You have two honest choices once a line is deprecated and removed from the maintained list: pay for vendor help or move forward.
Drop-In Replacement from HeroDevs
HeroDevs is ESLint's partner for retired lines. Its drop-in replacement for v8 adds never-ending support, and HeroDevs publishes security fixes without a rewrite. Teams that cannot finish a migration yet can start there.
Tidelift Commercial Support for Active Lines
Tidelift is ESLint's partner for lines that are still maintained, while HeroDevs covers retired ones such as v8, so pick the vendor that matches your version.
Plugin Compatibility and Breaking Changes
The move to v9 brought breaking changes and a new config format. An upgrade off a retired line stalls when a plugin or TypeScript parser lags; Shopify's Hydrogen project was held up this way on v8. Check each of your plugins before you move v8 or v9 projects to v10, where updates keep flowing.