Rules and languages

The Sonar Rules catalog is the entry point where you can discover all the existing rules. While running an analysis, SonarLint raises an issue every time a piece of code breaks a coding rule. 

Issues in your code are linked to Clean Code code attributes. When an issue is detected, it signifies that this part of your code is not consistent, intentional, adaptable, or responsible enough and that it impacts one or multiple software qualities. 

For more information about Clean Code attributes and software qualities, check out the Clean Code introduction page.

Overview

supported language versions

SonarLint provides analysis for several languages. Support for your language may vary depending on the SonarLint version you're running. 

The table below lists the supported language and language versions. For each language version, the level of support is defined as follows: 

• Fully supported: Analysis will complete. All the language features are understood and examined.
• Not supported: Analysis might break, there is no guarantee it will complete.
• Supported: Everything between fully supported and not supported.

For language-specific properties, refer to the relevant language page in SonarQube and SonarCloud directly, as the same Sonar language analyzers are used by SonarLint.

Supported out of the box: SonarLint automatically checks your code in these languages and formats.
Connected Mode required: Running in Connected Mode with SonarQube or SonarCloud unlocks analysis for these languages and formats.

Language		Supported version
Apex rules		-
Azure Resource Manager rules		-
C rules		C89, C99, C11, C17: Fully supported C23: Supported GNU extensions: Supported
		-
C++ rules		C++20, C++23: Supported C++03,  C++11, C++14, C++17: fully supported  GNU extensions: Supported
C# rules		C#1 to C#12: Fully supported
CloudFormation		2010-09-09: Supported
COBOL rules		See below for additional requirements.
CSS rules		-
Docker		-
Go rules		-
HTML rules		-
Java rules		Java LTS versions 8 to 21, and all intermediate versions: Fully supported
JavaScript rules		ECMAScript 2022 and all previous versions: Supported
Kubernetes		-
PHP rules		5.x, 7.x, and 8.3: Fully supported
PL/SQL rules		-
Python and IPython notebook rules		2.7: supported 3.0 to 3.12: Fully supported
Secrets detection rules		-
T-SQL rules		-
Terraform		-
TypeScript rules		TypeScript 5.6 and all previous versions: Supported

The full list of available rules can be found in the VS Code UI. Go to the SONARLINT RULES view of the SonarLint view container; here you can activate and deactivate rules to match your conventions. SonarLint will also offer a code action on each issue to quickly deactivate the corresponding rule.

Connected Mode syncs your SonarQube or SonarCloud quality profile with the local analysis to suppress issues reported in the IDE; as a general rule, the server settings will override any settings defined in the IDE. Look at the Connected Mode documentation for more information.

For more details about languages and new features under consideration for VS Code, check out the SonarLint roadmap where we list our coming soon and newly released features.

Rule selection

Sonar Rules can individually be turned on or off while running SonarLint in standalone mode. Simply go to SonarLint > RULES view in the VS Code Activity Bar and deactivate or activate rules at will. Each rule is clearly marked as on or off, and it's possible to filter the visible list by an Active, All, and Inactive status.

When your project is bound to SonarQube or SonarCloud using Connected Mode, the rule set is managed on the server side as defined by the quality profile. 

Sonar Rule Descriptions

Simply right-click an issue in the PROBLEMS Panel, and choose SonarLint: Open description of rule `...` to open the SonarLint Rule Description webview. Here you will find a brief explanation of the rule, along with a noncompliant and compliant code example.

For some SonarLint Rule Descriptions, you are able to visualize a diff view for the noncompliant and compliant code sample which should help you fix your issue.

An issue’s Clean Code attribute, software qualities, and severity are presented to you when opening the SonarLint Rule Decriptions webview. Below the rule title, you will find the Clean Code issue badges that highlight an Issue’s Clean Code classification. Be sure to check out the Investigating issues page for more details about how issues appear in your IDE. 

Check the Clean Code definition page for details about Clean Code attributes, and the Clean Code benefits page to better understand software qualities for more details about how they help classify your issue. 

Applying rules while in Connected Mode

Connected Mode syncs your SonarQube or SonarCloud Quality Profile with the local analysis to suppress issues reported in the IDE. See the Connected Mode documentation for more information.

Language-specific requirements

JS/TS/CSS analysis

To analyze JavaScript, TypeScript, or CSS code, SonarLint requires Node.js executable. The minimal supported version is 18.18 for standalone analysis or in Connected Mode with SonarCloud. For Connected Mode with SonarQube, it depends on the version of the JS/TS analyzer on your SonarQube server. SonarLint will attempt to automatically locate node, or you can force the location using:

    {
        "sonarlint.pathToNodeExecutable": "/home/yourname/.nvm/versions/node/v18.18/bin/node"
    }

Analysis of TypeScript in Connected Mode with SonarQube requires the server to use version 8.1 or above.

C and C++ analysis-specific requirements

To analyze C and C++ code, SonarLint requires that you define a path to your compile commands json file:

{
        "sonarlint.pathToCompileCommands": "/home/yourname/repos/proj/compile_commands.json"
    }

Search for Path To Compile Commands in the VS Code Settings (or go to VS Code > Settings > Settings > Extensions > SonarLint > User and scroll to the entry); then enter the full path to your active compilation database:

Note: if you are using Microsoft Visual C++ compiler, the environment should be ready to build the code. For example, by launching VS Code from your Visual Studio Command Prompt. 

More information about supported environments and troubleshooting C & C++ analysis can be found on the Running an analysis page.

COBOL analysis

COBOL analysis is a feature available in SonarLint for VS Code v3.19+ when running in Connected Mode with SonarQube Enterprise edition+ or SonarCloud. In addition, the VS Code Language Mode must be set to COBOL independent of your file type. If your extension doesn’t set the language automatically, please see the VS Code documentation to learn how to manually change the language for the selected file.

By default, SonarLint takes the analysis configuration from the SonarQube or SonarCloud server therefore it is required that your project has already been analyzed by SonarQube or SonarCloud. The following COBOL analyzer properties are synced by default unless previously overridden locally. Note that all properties found on the server will be synced locally, not just this selection:

• sonar.cobol.dialect
• sonar.cobol.file.suffixes
• sonar.cobol.sourceFormat
• sonar.cobol.copy.suffixes
• sonar.cobol.copy.directories

In case copybooks are in different location locally, the analyzer property sonar.cobol.copy.directories should be defined in the /project/.vscode/settings.json file.

If working with COBOL files via Zowe explorer, it is recommended to update your Zowe workspace settings in VS Code by modifying the temporary file location; temporary files should be saved to your project folder which is bound to SonarQube or SonarCloud. With the correct configuration, the analysis will be executed normally and you should see detected problems.

C# analysis

C# analysis is available in SonarLint for VS Code v4.0+. More information will be found in the C# configuration collapsible below:

Infrastructure as Code

SonarLint for VS Code 3.17+ supports analysis of Infrastructure as Code (IaC) to help you secure your deployments. See the Sonar Rules pages as linked below for complete details:

• Azure Resource Manager
• Cloud formation
• Docker
• Kubernetes
• Terraform

Java analysis

To enable the support for Java analysis, you need the Language support for Java VSCode extension (version 0.56.0 or higher). You also need to be in standard mode.

Apex analysis

The support for Apex analysis is only available together with SonarQube Enterprise Edition or SonarCloud when running in Connected Mode. You will also need the Salesforce Extension Pack VS Code extension.

PL/SQL analysis

The support for PL/SQL analysis is only available together with Commercial Editions of SonarQube or with SonarCloud when running in Connected Mode. You also need the Oracle Developer Tools for VSCode VS Code extension.

Python

Jupyter Notebooks in VS Code

SonarLint for VS Code v3.16+ supports analysis of Python code inside Jupyter notebooks. When opening an .ipynb file, SonarLint analyzes the Python code and Python cells inside your Jupyter Notebooks.

There is nothing special to do to run a SonarLint analysis; simply open a Jupyter Notebook file. As with any Jupyter Notebook, you must set up your VS Code environment to run a project. The usual Quick Fix and issue investigation options you are accustomed to are available.

Managing rules

IPython Notebooks is a new rules category in the SonarLint explorer. Go to SONARLINT RULES > IPython Notebooks in the SonarLint view container to enable/disable rules, just as you would any rule for other languages.

The following rules have been disabled by default for Jupyter documents because they tend to be noisy in the notebook environment:

• ipython:S905, ipython:S1481, ipython:S2201, ipython:S5754

Connected Mode

Connected Mode will be ignored when working with Jupyter Notebooks. You will only have local analysis; this is because analysis of Jupyter Notebooks is not yet supported by SonarQube or SonarCloud.

Magic commands

All Magic commands are ignored by SonarLint (for example, %matplotlib inline and %%timeit). When a line magic command is found, that line will be ignored. Similarly, when a cell magic command is found, the entire cell will be ignored. The next image below shows a normal Jupyter cell; the second image illustrates the same cell with a cell magic command. Note how SonarLint ignores issues in the cell with the magic command.

T-SQL

T-SQL analysis is available running with Connected Mode with Commercial Editions of SonarQube, or with SonarCloud. 

Some configuration may be required on the server side; please see the SonarQube and SonarCloud documentation pages about T-SQL analysis for complete details.

Other rule types

DBD rules

Dataflow bugs (DBD) are what Sonar calls a series of advanced Python and Java bugs using symbolic execution. This type of issue can cause runtime errors and crashes in Python and Java. If you want to learn more, check out our blog post for a good explanation with an example.

DBD rules for Python and Java are supported in Commercial Editions of SonarQube. At this time, SonarLint for VS Code supports DBD detection for Python when running in Connected Mode with SonarQube Active versions; support for DBD detection in Java is under development.

Injection vulnerabilities

Security vulnerabilities requiring taint engine analysis (taint vulnerabilities) are only available in Connected Mode because SonarLint pulls them from SonarQube or SonarCloud following a project analysis.

To browse injection vulnerabilities in SonarLint for VSCode, configure Connected Mode with your SonarQube Developer Edition (and above) or SonarCloud instance. Once a Project Binding is configured, SonarLint will synchronize with the SonarQube or SonarCloud server to report the detected injection vulnerabilities.

More information about security-related rules is available in the SonarQube or SonarCloud documentation.

Security hotspots

In SonarLint for VS Code 3.14 and above, local detection of Security Hotspots is enabled if you are using Connected Mode with SonarQube 9.9+ or SonarCloud.

Please see the SonarLint documentation on Security hotspots for more details.

Secrets detection

Secrets are pieces of user-specific or system-level credentials that should be protected and accessible to legitimate users only. SonarLint detects exposed Secrets in your source code and language-agnostic config files. When running in Connected Mode, the SonarQube or SonarCloud Quality Profiles are applied to locally detected Secrets.