Analyze a set of files
You can run SonarLint on specific files, or even analyze all VCS-changed files. Find these options under the usual IntelliJ Analyze menu.
Use SonarLint
in IntelliJ IDEA
- Version 4.6
- Released April 2020
- Plugin Repository
Detect Code Quality and Security issues on the fly in:
Python 
Kotlin 
Ruby 
ScalaOnly available together with:
SwiftOnly available together with:
Only available together with:
Benefit from a full integration
Review highlighted issues in the editor
Use the SonarLint window to review issues
Hook SonarLint to pre-commit checks
And go further
Out-of-the-box, SonarLint reports issues on the files you're editing.
There are a few more options you can use if you wish.
Exclude specific files and issues
You can tell SonarLint which files should not be analyzed. Just right-click on any file, or manage File Exclusions at project level (Configure SonarLint action).
Enable more rules, or mute some
In the SonarLint General Settings you can choose which rules should be active or not. You can also mute rules on-the-fly via a quick-fix option, or from the list of issues.
Find logs if you need them
Under the SonarLint window in the Logs tab.
SonarLint can be used together with SonarQube or SonarCloud, allowing your team
to always be on the same page when it comes to Code Quality and Security.
Your team on the same page
- All the team uses the same code quality
and security rules - Project settings (such as code exclusions)
are shared at team level - Team members are notified if a breaking
change makes it in the main branch
Additional language support!
- Scala
- Swift
I’m in! How do I activate this in SonarLint?
First connect to a server via the SonarLint General Settings,
then bind the project under SonarLint Project Settings.
Open Source
Visit our issue tracker, fork SonarLint on GitHub and submit pull requests.
Latest News
TypeScript code can now be analyzed in JetBrains IDEs! Lean more
Feedback welcome
Get in touch and share feedback on SonarSource Community Forums.