ESLint 1 · Version Status
ESLint 1 End of Life Date
ESLint 1 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
ESLint 1 is past end of life. This version no longer receives security patches. 3739 days past EOL — migrate to a supported version immediately.
EOL Date
Aug 12, 2016
3739 days past EOL
Latest Release
1.10.3
Standard release
Release Date
Jul 31, 2015
ESLint 1 series
Where these dates come from
End of lifeAug 12, 2016Vendor's own page, checked by a person · eslint.org · checked Nov 1, 2026high · 2 sources agree End of active supportFeb 12, 2016Vendor's own page, checked by a person · eslint.org · checked Nov 1, 2026high · 2 sources agree ReleaseJul 31, 2015Vendor's own page, checked by a person · eslint.org · checked Nov 1, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
ESLint 1 was released on July 31, 2015 and support ended on August 12, 2016 — a supported lifespan of 1 year, shorter than the 1 year and 6 months median for ESLint releases. Its latest release on record is 1.10.3, published December 1, 2015 — 9 months before support ended. It has been past its end-of-life date for 10 years and 3 months. 7 newer ESLint releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
| Version | Latest | EOL Date | Status |
|---|
| → 1 |
1.10.3 |
Aug 12, 2016 |
EOL |
| 2 |
2.13.1 |
Jan 1, 2017 |
EOL |
| 3 |
3.19.0 |
Dec 11, 2017 |
EOL |
| 4 |
4.19.1 |
Dec 22, 2018 |
EOL |
| 5 |
5.16.0 |
Dec 21, 2019 |
EOL |
| 6 |
6.8.0 |
Nov 8, 2020 |
EOL |
| 7 |
7.32.0 |
Apr 9, 2022 |
EOL |
| 8 |
8.57.1 |
Oct 5, 2024 |
EOL |
What does ESLint 1 end of life mean?
When ESLint 1 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running ESLint 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to ESLint 10 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does ESLint 1 reach end of life?
ESLint 1 reached end of life on August 12, 2016. This version is no longer receiving security patches.
Is ESLint 1 still supported?
No. ESLint 1 reached end of life on August 12, 2016 and is no longer receiving security patches.
What should I upgrade to from ESLint 1?
The recommended upgrade from ESLint 1 is
ESLint 10 — the latest actively supported version. Check the
ESLint full timeline for all supported versions.
What are the security risks of running ESLint 1 past EOL?
Since ESLint 1 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL ESLint should migrate immediately or implement compensating controls.