Complete end-of-life dates, support windows, and security status for all Eslint versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.10.3 | Jul 31, 2015 | Aug 12, 2016 | 3557 days past EOL | EOL |
| 2 | 2.13.1 | Feb 12, 2016 | Jan 1, 2017 | 3415 days past EOL | EOL |
| 3 | 3.19.0 | Jul 1, 2016 | Dec 11, 2017 | 3071 days past EOL | EOL |
| 4 | 4.19.1 | Jun 11, 2017 | Dec 22, 2018 | 2695 days past EOL | EOL |
| 5 | 5.16.0 | Jun 22, 2018 | Dec 21, 2019 | 2331 days past EOL | EOL |
| 6 | 6.8.0 | Jun 21, 2019 | Nov 8, 2020 | 2008 days past EOL | EOL |
| 7 | 7.32.0 | May 8, 2020 | Apr 9, 2022 | 1491 days past EOL | EOL |
| 8 | 8.57.1 | Oct 9, 2021 | Oct 5, 2024 | 581 days past EOL | EOL |
| 9 | 9.39.4 | Apr 5, 2024 | Aug 6, 2026 | 89 days remaining | Warning |
| 10 | 10.3.0 | Feb 6, 2026 | Already EOL | Supported | Active |
When a Eslint version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Eslint should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →