EOL.Wiki EOL.Wiki
← ← Back to all products

ESLint

Active
Tools & Monitoring Latest Version: 10.0.0 Latest Release: Feb 6, 2026

ESLint is a pluggable JavaScript and TypeScript linting utility for identifying and fixing code problems.

Versions

10

Latest Version

10.0.0

Active Support

2

EOL

8

Lifecycle Timeline

Today
10
10
9
9
8
8
7
7
6
6
5
5
4
4
3
3
2
2
1
1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
10Feb 6, 2026YesNo10.0.0No
Active
9Apr 5, 2024YesAug 6, 20269.39.2No
Active
8Oct 9, 2021Apr 5, 2024Oct 5, 20248.57.1No
EOL
7May 8, 2020Oct 9, 2021Apr 9, 20227.32.0No
EOL
6Jun 21, 2019May 8, 2020Nov 8, 20206.8.0No
EOL
5Jun 22, 2018Jun 21, 2019Dec 21, 20195.16.0No
EOL
4Jun 11, 2017Jun 22, 2018Dec 22, 20184.19.1No
EOL
3Jul 1, 2016Jun 11, 2017Dec 11, 20173.19.0No
EOL
2Feb 12, 2016Jul 1, 2016Jan 1, 20172.13.1No
EOL
1Jul 31, 2015Feb 12, 2016Aug 12, 20161.10.3No
EOL

Frequently Asked Questions

Which versions of ESLint have reached end of life?
The following ESLint versions have reached end of life and no longer receive security updates: 8, 7, 6, 5, 4, 3, 2, 1. It is recommended to upgrade to a supported version.
Is it safe to continue using ESLint 8?
ESLint 8 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of ESLint?
The latest version of ESLint is 10.0.0, released in the 10 release cycle.
How many versions of ESLint are currently supported?
ESLint currently has 2 actively supported version(s): 10, 9.
When does ESLint 10 reach end of life?
ESLint 10 does not have a specific end-of-life date announced yet.
What should I do when ESLint reaches end of life?
When a ESLint version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.