3.5.0 • Public • Published

NPM module to run SonarQube/SonarCloud analyses

sonarqube-scanner makes it very easy to trigger SonarQube / SonarCloud analyses on a JavaScript code base, without needing to install any specific tool or (Java) runtime.

This module is analyzed on SonarCloud.

Quality Gate Maintainability Reliability Security Releases


Prerequisite: Node v16+ (otherwise use sonarqube-scanner v2.9.1)

This package is available on npm as: sonarqube-scanner

To add code analysis to your build files, simply add the package to your project dev dependencies:

npm install -D sonarqube-scanner

To install the scanner globally and be able to run analyses on the command line:

npm install -g sonarqube-scanner

Usage: add code analysis to your build files

Prerequisite: you've installed the package as a dev dependency.

The following example shows how to run an analysis on a JavaScript project, and pushing the results to a SonarQube instance:

const scanner = require('sonarqube-scanner');

    serverUrl: '',
    token: '019d1e2e04eefdcd0caee1468f39a45e69d33d3f', // use "login" for SQ up to version 9
    options: {
      'sonar.projectName': 'My App',
      'sonar.projectDescription': 'Description for "My App" project...',
      'sonar.sources': 'src',
      'sonar.tests': 'test',
  () => process.exit(),

Syntax: sonarqube-scanner ( parameters, [callback] )


  • parameters Map
    • serverUrl String (optional) The URL of the SonarQube server. Defaults to http://localhost:9000
    • login String (optional) The login used to connect to the SonarQube server up to version 9. Empty by default.
    • token String (optional) The token used to connect to the SonarQube server v10+ or SonarCloud. Empty by default.
    • caPath String (optional) the path to a CA to pass as https.request() options.
    • options Map (optional) Used to pass extra parameters for the analysis. See the official documentation for more details.
  • callback Function (optional) Callback (the execution of the analysis is asynchronous).

Usage: run analyses on the command line

Prerequisite: you've installed the package globally.

If you want to run an analysis without having to configure anything in the first place, simply run the sonar-scanner command. The following example assumes that you have installed SonarQube locally:

cd my-project

Specifying properties/settings

  • If there's a package.json file in the folder, it will be read to feed the analysis with basic information (like project name or version)

  • If there's a file in the folder, it will behave like the original SonarScanner

  • Additional analysis parameters can be passed on the command line using the standard syntax

    • Example:

      sonar-scanner -Dsonar.token=019d1e2e04e

Usage: run analyses with npx

To run analyses without explicitly installing the scanner, run the following command instead:

npx sonarqube-scanner

Similar to the above, you can specify analysis properties and settings using either a package.json file, a file, or command line arguments.


I constantly get "Impossible to download and extract binary [...] In such situation, the best solution is to install the standard SonarScanner", what can I do?

You can install manually the standard SonarScanner, which requires to have a Java Runtime Environment available too (Java 8+).

It is important to make sure that the SonarScanner $install_directory/bin location is added to the system $PATH environment variable. This will ensure that sonar-scanner command will be resolved by the customScanner, and prevent the error:

Error: Local install of SonarScanner not found.
    at getLocalSonarScannerExecutable (<project_dir>/node_modules/sonarqube-scanner/src/sonar-scanner-executable.js:153:11)
    at scanUsingCustomScanner (<project_dir>/node_modules/sonarqube-scanner/src/index.js:52:3)

Once local installation is done, you can replace the 2nd line of the example:

var scanner = require('sonarqube-scanner').customScanner;

In my Docker container, the scanner fails with ".../jre/bin/java: not found", how do I solve this?

You are probably relying on Alpine for your Docker image, and Alpine does not include glibc by default. It needs to be installed manually.

Thanks to Philipp Eschenbach for troubleshooting this on issue #59.

Download From Mirrors

By default, the scanner binaries are downloaded from To use a custom mirror, set $SONAR_SCANNER_MIRROR. Or download precise version with $SONAR_SCANNER_VERSION



or alternatively set variable in .npmrc


For mirrors using Basic HTTP authentication (e.g. Sonatype Nexus 3 raw-proxy, Artifactory with artifactory-cache-proxy), simply specify the username and password as part of the URL:


Proxy authentication is supported as well, see below.

Specifying the cache folder

By default, the scanner binaries are cached into $HOME/.sonar/native-sonar-scanner folder. To use a custom cache fodler instead of $HOME, set $SONAR_BINARY_CACHE.


export SONAR_BINARY_CACHE=/Users/myaccount/cache

or alternatively set variable in .npmrc


Download behind proxy

In order to be able to download binaries when you're behind a proxy it will be enough to set the http_proxy or https_proxy environment variable. Both support proxies using plain HTTP or HTTPS.


export http_proxy=
export https_proxy=

export http_proxy=
export https_proxy=

Behind authenticated proxy:

export http_proxy=
export https_proxy=

export http_proxy=
export https_proxy=


sonarqube-scanner is licensed under the LGPL v3 License.

Package Sidebar


npm i sonarqube-scanner

Weekly Downloads






Unpacked Size

43 kB

Total Files


Last publish


  • lpaulger_sonarsource
  • gabssnake
  • lucio.merotta.sonarsource
  • jcarsique-sonar
  • saberduck
  • elena-vilchik
  • andrea-guarino-sonarsource
  • gregaubert
  • sonar-jay
  • philippe-perrin-sonarsource
  • xay.tanovan
  • wouter-admiraal-sonarsource
  • mathieu-sonar
  • antonio.garcia.sonarsource
  • tomverin
  • yassin-kammoun-sonarsource
  • sonartech