Is SonarLint Deprecated? No - Here's What Actually Happened

The short answer

SonarLint is not deprecated. It was renamed to SonarQube for IDE on October 29, 2024. The extension is actively maintained, still free, still open source under LGPL-3.0, and still supports VS Code, Visual Studio, Eclipse, and the JetBrains family. Nothing was discontinued.

If you searched this because your IDE showed a deprecation-flavoured notice, or because a marketplace listing looked abandoned, you ran into a naming migration rather than an end-of-life.

What actually changed

Sonar - the company, which itself shortened its name from SonarSource - rebranded its entire product family in late 2024. The old names were genuinely confusing: three products with three different prefixes doing related jobs in different places.

Old name	New name	What it is
SonarLint	SonarQube for IDE	The free extension that lints as you type
SonarQube	SonarQube Server	The self-hosted analysis server
SonarCloud	SonarQube Cloud	The hosted SaaS version
(new)	SonarQube Community Build	The free self-hosted edition

The logic is a single brand plus a suffix for where the thing runs. Once you see it laid out, it is clearly better than what came before. It also means a decade of tutorials, Stack Overflow answers, and internal wiki pages now use names that no longer appear in any marketplace.

Why it looks deprecated when it is not

Three things create the false signal.

The repo and extension IDs never changed. The VS Code extension is still published under the ID SonarSource.sonarlint-vscode, and the GitHub repository is still sonarlint-vscode. So you can land on a page titled “SonarQube for IDE” whose URL and identifier both say sonarlint, which reads like an abandoned redirect.

Old listings and forks linger. Search results still surface pre-2024 pages, mirrors, and third-party plugin directories that were never updated. Some of those genuinely are dead. The official one is not.

The community still says SonarLint. Two years on, most developers, most blog posts, and most CI configs still use the old name. That is normal for a rebrand this size and it does not indicate anything about support status.

How to check for yourself

The fastest way to confirm a tool is alive is release cadence, not marketing pages.

• JetBrains: open plugin 7973 in the marketplace and look at the version history. There are releases through mid-2026.
• VS Code: the extension listing shows the last-updated date directly under the install button.
• GitHub: check the commit history on the sonarlint-vscode repository rather than the README.

A deprecated project has a pinned notice, a stale last commit, and an archived badge. None of those are present here.

What SonarQube for IDE gives you free

Standalone mode - no server, no account - covers 20+ languages with a curated subset of the full ruleset. It flags issues in the editor as you type, before anything reaches a pull request.

Connected mode is where it gets more interesting. Point the extension at a SonarQube Server or Cloud instance and it pulls down the full ruleset, your team’s Quality Profile, project-specific exclusions, and in commercial editions the taint analysis rules. Your IDE then flags exactly what CI would flag, which removes the most annoying failure mode in code quality tooling: a clean local run and a red pipeline.

The extension itself stays free in both modes. What costs money is the server-side licence for the commercial editions.

The part that matters more in 2026

Because it is built on the VS Code extension architecture, SonarQube for IDE runs inside the AI-native editors that fork VS Code - Cursor, Windsurf, and Trae among them.

That combination is worth thinking about deliberately. An AI assistant generates code quickly and describes it confidently. A deterministic rule engine has no opinion about how plausible the code looks; it either matches a known-bad pattern or it does not. Running one inside the other means the assistant’s confident-but-wrong output gets checked by something that cannot be talked into agreeing.

This is the same argument for pairing an AI reviewer with static analysis at the PR stage, just moved earlier - our static code analysis guide covers how the two layers divide the work.

What to do

If you already have it installed: nothing. It updates in place. The name in your extensions panel will change and everything else stays where it was.

If you are installing fresh: search for “SonarQube for IDE” in your editor’s marketplace. If you search for SonarLint you will still find it, because the listing keeps the old name as an alias.

If your CI or docs reference SonarLint: they still work. Rename them when you happen to be in the file, not as a project.

If you are choosing between this and a full analysis setup: the IDE extension is a complement, not a replacement. It gives fast local feedback on a curated ruleset. It does not give you quality gates, historical debt tracking, or pull request decoration. For that you need SonarQube Server, Cloud, or Community Build - and our SonarQube review covers where each of those makes sense.

Bottom line

The tool you are looking for is alive, free, and shipping releases. It just has a different name on the box than it did when you last installed it.

The genuinely useful takeaway is smaller than the search query suggests: when a widely used developer tool appears to have vanished, check the release history before you go looking for a replacement. Rebrands produce far more phantom deprecations than actual ones.