Skip to end of metadata
Go to start of metadata

By SonarSource – SonarSource – Issue Tracker – Supported by SonarSource
More versions
SonarSwift 4.1 – Jan 07, 2019 – SonarQube 6.7+ (Compatible with LTS)
Support for Swift 5.0, Rules S1451 and S2201 Improvements
I accept the Terms and ConditionsDownloadRelease notes


SonarSwift detects bugs, vulnerabilities and code smells in Swift code up to Swift 4.2 (provided with Xcode 10) and the upcoming Swift 5.

First Analysis of a Swift 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 SonarSwift (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:



Advanced Usage

With SonarSwift, you can also:



  • No labels