Linters · 6 tools
Top 6 editor linting tools for getting lint feedback while writing code
If you want lint feedback while you type, start with SonarLint (now called SonarQube for IDE), Ruff and ESLint. This shortlist is for individual developers and teams standardizing editor setups, and it runs from multi-language tooling to linters focused on a single language family such as Ruby, shell or CSS.
| # | Tool | Best for | Key feature | Platforms / deployment | Pricing | More |
|---|---|---|---|---|---|---|
| 1 | SonarLintSonar | Mixed-language teams that want one extension across several IDEs | Over 20 languages analyzed in real time | Visual Studio, VS Code, Eclipse, JetBrains IDEs, VS Code-based AI-native editors, GitHub Codespaces and GitPod | See vendor pricing page | Introduction |
| 2 | RuffAstral | Python developers and monorepo teams working in VS Code | Language server with real-time diagnostics that refresh when configuration files change | First-party editor integrations, including VS Code | See vendor pricing page | Official site |
| 3 | ESLintESLint | JavaScript and JSX teams enforcing code quality | Built into most text editors | Most text editors; specific editors not listed on official pages | See vendor pricing page | Introduction |
| 4 | RuboCopRuboCop | Ruby teams enforcing a shared style guide | Built-in language server with live offenses and quick fixes | Editors that connect to its built-in language server; specific editors not stated on official pages | See vendor pricing page | Introduction |
| 5 | ShellCheckShellCheck | Developers writing shell scripts who want inline warnings | Detects many kinds of quoting issues | Major editors as an integrated linter; installable with several package managers | See vendor pricing page | Introduction |
| 6 | StylelintStylelint | Teams enforcing CSS conventions across stylesheets and embedded styles | Over 150 built-in rules for modern CSS | Not stated on official pages | See vendor pricing page | Introduction |
1 SonarLint
By Sonar
SonarLint, now called SonarQube for IDE, is an editor extension from Sonar that gives real-time analysis, quick-fix guidance and security issue detection as you code. It detects bugs, code smells, vulnerabilities and security hotspots.
Why it is here: It comes first because it documents the widest language coverage in the editor, with over 20 languages analyzed in real time plus frameworks and infrastructure-as-code platforms.
- Best for
- Mixed-language teams that want one extension across several IDEs
- Key features
- Over 20 languages analyzed in real time
- Visual Studio, VS Code, Eclipse and JetBrains IDE support
- Connected Mode syncs rules and quality gates from SonarQube Server or SonarQube Cloud
- In-editor explanations, rule details and code examples
- Focus-on-new-code setting filters the issue list
- Limits
- Additional languages such as COBOL, Apex and PL/SQL are documented as available in Connected Mode, so teams that need them should check the vendor documentation for the connection requirements.
- Platforms / deployment
- Visual Studio, VS Code, Eclipse, JetBrains IDEs, VS Code-based AI-native editors, GitHub Codespaces and GitPod
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (sonarsource.com/products/sonarlint) · Read our introduction to SonarLint
2 Ruff
By Astral
Ruff is a Python linter and code formatter written in Rust and backed by Astral. Its language server provides real-time diagnostics in the editor.
Why it is here: It follows SonarLint because, although it is Python-focused, it documents editor features beyond plain .py files, including Markdown code blocks and Jupyter Notebooks.
- Best for
- Python developers and monorepo teams working in VS Code
- Key features
- Language server with real-time diagnostics that refresh when configuration files change
- Over 900 built-in rules, including re-implementations of popular Flake8 plugins
- Drop-in parity with Flake8, isort and Black
- Code actions such as ignoring a diagnostic with a noqa comment
- Formats a whole document or a range of lines
- Limits
- Documented for Python and related files such as notebooks and Markdown code blocks. Teams that need other languages in the same editor should pair it with other linters.
- Platforms / deployment
- First-party editor integrations, including VS Code
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
3 ESLint
By ESLint
ESLint is an open source, pluggable and configurable linter that finds and reports problems in JavaScript and JSX through static analysis.
Why it is here: It sits third because it covers browser and server JavaScript, with or without a framework, and now officially supports linting shell scripts as a step toward a language-agnostic platform.
- Best for
- JavaScript and JSX teams enforcing code quality
- Key features
- Built into most text editors
- Syntax-aware automatic fixes rather than find-and-replace
- Custom parsers, preprocessing and user-written rules
- Works for browser and server JavaScript, with or without a framework
- Also runs in continuous integration pipelines
- Limits
- Documented primarily for JavaScript and JSX, with shell script linting newly supported. Teams that need other languages should check the vendor documentation.
- Platforms / deployment
- Most text editors; specific editors not listed on official pages
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (eslint.org) · Read our introduction to ESLint
4 RuboCop
By RuboCop
RuboCop is a Ruby linter and code formatter based on the community Ruby Style Guide. It includes a built-in language server that gives editors live offenses and quick fixes.
Why it is here: It is placed here because its editor coverage is limited to Ruby, though it offers a built-in language server and plugins that add framework and library knowledge.
- Best for
- Ruby teams enforcing a shared style guide
- Key features
- Built-in language server with live offenses and quick fixes
- Cops grouped in departments such as Lint, Style, Layout, Naming, Metrics and Security
- rubocop -a applies only corrections that cannot change code behaviour
- Single .rubocop.yml that can inherit from a shared config
- --auto-gen-config records existing offenses to ease adoption on old codebases
- Limits
- Documented for Ruby only. The optional project index for cross-file checks is described as experimental and requires Ruby 3.2 or newer.
- Platforms / deployment
- Editors that connect to its built-in language server; specific editors not stated on official pages
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (rubocop.org) · Read our introduction to RuboCop
5 ShellCheck
By ShellCheck
ShellCheck is an open source static analysis tool, written in Haskell, that finds bugs in shell scripts. It is supported as an integrated linter in major editors.
Why it is here: It sits fifth because its editor use is limited to shell scripts, although it detects higher-level semantic problems, many kinds of quoting issues and portability problems when the shebang says sh.
- Best for
- Developers writing shell scripts who want inline warnings
- Key features
- Detects many kinds of quoting issues
- Detects higher-level semantic problems
- Warns about portability problems when the shebang says sh
- Can be tried online by pasting a script
- Documented on the ShellCheck Wiki
- Limits
- Documented for shell scripts only, and the official pages do not name specific editors. Check the ShellCheck Wiki for setup in your editor.
- Platforms / deployment
- Major editors as an integrated linter; installable with several package managers
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (shellcheck.net) · Read our introduction to ShellCheck
6 Stylelint
By Stylelint
Stylelint is a CSS linter that helps avoid errors and enforce conventions. It can parse CSS-like languages and extract embedded styles from other file types.
Why it is here: It closes the list because its editor use is limited to stylesheets, though it handles SCSS, Sass, Less, SugarSS and styles embedded in HTML, Markdown and CSS-in-JS.
- Best for
- Teams enforcing CSS conventions across stylesheets and embedded styles
- Key features
- Over 150 built-in rules for modern CSS
- Detects unknown things such as misspelled property names
- Detects invalid constructs such as malformed grid areas
- Shareable configs and plugins for custom rules
- Automatically fixes problems where possible
- Limits
- The official pages in our facts do not describe editor integrations, so teams should check the Stylelint documentation for editor setup. The project recommends using a pretty printer like Prettier alongside it.
- Platforms / deployment
- Not stated on official pages
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (stylelint.io) · Read our introduction to Stylelint
How we chose these tools
We looked at three things: fit with the use case of getting lint feedback in the editor while writing code, the capabilities each vendor documents, and what the official pages say about editors, language servers and platforms. A tool needed a documented editor path to make the list. Language coverage in the editor guided the order, with multi-language extensions first and single-language linters after them.
All facts come from official vendor pages, each with a recorded check date. The order reflects editorial fit for this specific use case and is not a statement that any tool is better overall. This list is built from documentation rather than product trials, so confirm editor versions, setup steps and rule coverage against the vendor documentation before standardizing a team setup.
Order used in this guide: Ordered by breadth of language coverage in the editor, with multi-language extensions first.
Frequently asked questions
Which linter covers the most languages in the editor?
SonarLint (SonarQube for IDE) documents analysis of over 20 languages in real time, plus frameworks and infrastructure-as-code platforms. More languages such as COBOL, Apex and PL/SQL are available in Connected Mode.
Which linter gives real-time feedback for Python in VS Code?
Ruff has first-party editor integrations, including VS Code. Its language server provides real-time diagnostics and refreshes them when configuration files change.
Can I get lint feedback for shell scripts in my editor?
ShellCheck is supported as an integrated linter in major editors and finds bugs and quoting issues in shell scripts. ESLint also now officially supports linting shell scripts.
Can a linter in the editor use the same rules as my team's central projects?
SonarLint's Connected Mode links the IDE to SonarQube Server or SonarQube Cloud. Local analysis then uses the same rules and policies as the central projects, and rules and quality gates synchronize to the IDE.
Do these linters fix problems automatically?
Ruff, ESLint, RuboCop and Stylelint document automatic fixes, and SonarLint provides quick fixes. RuboCop's -a option applies only corrections that cannot change code behaviour, while -A also applies riskier ones.
- SonarLint: sonarsource.com/products/sonarqube/ide, sonarsource.com/solutions/ai — checked 21 November 2026
- Ruff: docs.astral.sh/ruff, docs.astral.sh/ruff/editors/features — checked 21 November 2026
- ESLint: eslint.org — checked 21 November 2026
- RuboCop: rubocop.org — checked 21 November 2026
- ShellCheck: shellcheck.net — checked 21 November 2026
- Stylelint: stylelint.io, stylelint.io/about/governance, stylelint.io/about/semantic-versioning — checked 21 November 2026
Linthelm is independent and not affiliated with the vendors listed. No vendor paid for inclusion or position. Product names belong to their owners. Features and prices change; confirm details on each official website.