Iris Code vs ESLint
ESLint checks how a line is written. Iris Code checks what the file has become.
The short answer
Iris Code finds the things a linter was never built to look for: a credential in the source, the same block pasted into four files, a dependency with a known CVE, and a health score that drops when the codebase degrades. It does that across ten languages, not just JavaScript. ESLint remains the best tool in the world for enforcing how JavaScript and TypeScript are written, and Iris Code does not try to replace it. Run both.
What ESLint is
ESLint is the standard open-source linter for JavaScript and TypeScript. It is free, highly configurable, autofixes much of what it finds, and has plugins for essentially every framework and style guide in the ecosystem. It is a rule engine for a language, not a code health tool.
What each one does.
8 of these rows go to Iris Code and 5 to ESLint. Both are in the table.
Pro is $6 a month where you are. Pricing is adjusted for purchasing power, so $6 is the ceiling and many countries pay less. See your rate.
Claims about ESLint were checked against its own published material on 18 August 2026. Pricing and features change. If anything here is out of date or wrong, tell us and it will be corrected.
Which one you should actually pick.
Choose Iris Code when
- You want to know about a committed credential, and ESLint has no opinion on those.
- Your repository is not only JavaScript, and you want one standard across Go, Python, Ruby, C#, Java, and Rust too.
- You want a number that moves when the codebase degrades, and a push blocked when it moves the wrong way.
- You want copy-pasted blocks surfaced, including the ones with the variables renamed.
- You want dependency CVEs in the same place as everything else.
Choose ESLint when
- You need style and correctness rules enforced consistently across a JavaScript or TypeScript codebase. Nothing else does this as well.
- You want to write custom rules specific to your codebase.
- You want autofix on save across hundreds of rules.
- You need framework-aware checks such as the rules of hooks.
Running both
This is the intended configuration, not a compromise. ESLint governs how a line is written; Iris Code governs what the file has become. Both publish to the Problems panel, both run in CI, and their findings do not overlap. If you have neither and have to start with one for a JavaScript codebase, start with ESLint.
Questions people ask.
Does Iris Code replace ESLint?
No, and it is not designed to. ESLint enforces style and language-level correctness through an enormous plugin ecosystem. Iris Code detects secrets, duplication, security anti-patterns, dependency vulnerabilities, and health regressions across ten languages. Removing ESLint in favour of Iris Code would lose coverage.
Will the two conflict in my editor?
No. Both publish diagnostics to the Problems panel under their own source label, and the rule sets do not overlap.
Can Iris Code run alongside ESLint in CI?
Yes. Iris Code ships a CLI that exits non-zero when the gate fails, so it sits next to an ESLint step in the same job.
Does Iris Code lint Go, Python, or Rust?
It analyses them, which is not the same thing. It does not replace gofmt and go vet, ruff, or clippy. It adds the cross-language layer those tools do not cover: secrets, duplication, dependency advisories, and a comparable health score.
Try it against your own code.
The free tier needs no account and no repository access. Install it, open a file, and see what it says.
Catch regressions before human review
Install Iris Code, set a threshold, and make every change answer to the same deterministic rules. Source analysis runs locally. The same rules run in VS Code, JetBrains IDEs, the iris CLI, hooks, and CI.