Buy it if you write TypeScript and use ESLint — it's free, it's the standard, and it replaces deprecated TSLint. Skip it only if you'd rather run one fast all-in-one tool like Biome or Oxlint.
Confidence
Medium. Based on 14 public sources
Ratings
Value for money
Ease of use
Feature depth
Support quality
Security posture
Pricing
$0
Open source
ModelNot disclosed
Monthly feesNot disclosed
HardwareNot disclosed
Free tierYes
Best for
→TypeScript codebases already on ESLint
→Teams migrating off deprecated TSLint
→React/Node projects needing typed linting
→CI code-quality gates
Not for
×JavaScript-only projects — plain ESLint is enough
×Anyone wanting one fast tool — use Biome or Oxlint
×Tiny scripts where linting is overkill
×Teams expecting built-in formatting — Prettier is separate
Gotchas - check before you buy
medium
Typed linting can slow big repos; performance issue documented since 2019.
medium
No vendor support — community issues and sponsors only, no SLA.
low
Formatting requires separate Prettier setup; expect tooling sprawl.
low
TSLint migration means mapping rules manually via their alternatives doc.
Pros and cons
Pros
+Free and open source; community-funded via OpenCollective.
+The standard TypeScript linting layer; replaces deprecated TSLint.
+Recommended single typescript-eslint package for ESLint 9 setups.
+Large community with abundant config guides and discussions.
+Dedicated public security page for the project.
Cons
−Typed linting runs slowly on some large projects.
−Configuration is fiddly; users trade many setup questions.
−Formatting needs Prettier separately — two tools to manage.
−Typed linting lags TypeScript 7 speed gains, per community reports.
Sources & method
- 14 sources - Actively maintained with a security page; sources show one reported vulnerable-dependency bug, no confirmed CVEs.
official x5review x4security x4news x1
Vulnerable minimatch dependency reported, GitHub issue flags dependence on a vulnerable minimatch package version.
Key stats
Value for money: 5/5
Rating
$0
Starting price
14
Sources
Analyzed
Value for money: 5/5. Free and open source, no paid tiers.
Ease of use: 3/5. Works, but config questions dominate forums.
Feature depth: 4/5. Deep TypeScript-aware rules; replaces deprecated TSLint.
Support quality: 3/5. Community GitHub and Reddit support, no vendor SLA.
Security posture: 3/5. Public security page; some dependency vulnerability reports.
$0 Price Open source, no paid tiers
Yes Free tier Entirely free, community-funded
v7+ packages ESLint compatibility Split packages recommended for ESLint 9+
Community-sponsored Funding Financial sponsors via OpenCollective
Pricing
Open source
$0
All parser, plugin, and utils packages
Community support via GitHub
Optional sponsorship via OpenCollective
Security
Actively maintained with a security page; sources show one reported vulnerable-dependency bug, no confirmed CVEs.
Vulnerable minimatch dependency reportedGitHub issue flags dependence on a vulnerable minimatch package version.⁷
What users say
Developers treat it as the default TypeScript linting choice, while citing setup effort and performance on large projects.
10.Do you guys use eslint on your typescript projects? https://www.reddit.com/r/typescript/comments/guiovl/do_you_guys_use_eslint_on_your_typescript_projects/
11.What is the best linting config for typescript? https://www.reddit.com/r/typescript/comments/1aoq5gb/what_is_the_best_linting_config_for_typescript/
12.TypeScript 7 is 10x faster, but typed linting still runs slow https://www.reddit.com/r/javascript/comments/1vq4r91/askjs_typescript_7_is_10x_faster_but_typed/
13.Why I Ditched ESLint + Prettier for Biome https://xergioalex.com/blog/why-i-ditched-eslint-prettier-for-biome/
14.Oxlint vs ESLint: Comparing JavaScript Linters https://betterstack.com/community/guides/scaling-nodejs/oxlint-vs-eslint/
Comments
One queue. No nested comments. Give a display name first. Limit: 200 words per comment and 7 comments per day. You can edit or delete yours.
No comments yet.