Skip to end of metadata
Go to start of metadata

By SonarSource – GNU LGPL 3 – Issue TrackerSources – Supported by SonarSource
More versions
SonarCSS 1.0.3 – Nov 23, 2018 – SonarQube 6.7+ (Compatible with LTS)
Remove noisy S4664 from "Sonar way"
DownloadRelease notes


SonarCSS allows you to scan your CSS, LESS and SCSS files.


  • Node.js >=6
  • You must not have other community plugin dealing with CSS installed on your SonarQube. If you have one, it will conflict with SonarCSS, so it should be removed.

First Analysis of a CSS Project

  1. Install SonarQube Server (see Setup and Upgrade for more details)
  2. Install SonarQube Scanner and be sure your can call sonar-scanner from the directory where you have your source code
  3. Install SonarCSS (see Installing a Plugin for more details)
  4. Run your analysis with the SonarQube Scanner by executing the following command from the root directory of the project:

    sonar-scanner -Dsonar.projectKey=xxx -Dsonar.sources=.
  5. Follow the link provided at the end of the analysis to browse your project's quality in SonarQube UI

Further Analyses

Assuming steps 1-3 above have already been completed, you'll want to encapsulate your analysis parameters in a file at the root of your project (see a sample project on GitHub: Then subsequent analyses can simply be run with:


SonarCSS Specific Properties


Can be used to explicitly set the location of Node.js executable. If not set analysis will use node from the PATH


List of suffixes for files to analyze. Default value is `.css,.less,.scss`

Advanced Usage

With SonarCSS, you can also:

  • No labels