Alternatives to SonarQube logo

Alternatives to SonarQube

ReSharper, Checkmarx, Codacy, FindBugs, and ESLint are the most popular alternatives and competitors to SonarQube.
552
272
+ 1
14

What is SonarQube and what are its top alternatives?

SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.
SonarQube is a tool in the Code Review category of a tech stack.
SonarQube is an open source tool with 4.3K GitHub stars and 1.2K GitHub forks. Here鈥檚 a link to SonarQube's open source repository on GitHub

SonarQube alternatives & related posts

ReSharper logo

ReSharper

71
20
0
71
20
+ 1
0
A Visual Studio extension for .NET and web developers
    Be the first to leave a pro
    ReSharper logo
    ReSharper
    VS
    SonarQube logo
    SonarQube
    Checkmarx logo

    Checkmarx

    6
    6
    0
    6
    6
    + 1
    0
    Unify your application security into a single platform
      Be the first to leave a pro
      Checkmarx logo
      Checkmarx
      VS
      SonarQube logo
      SonarQube

      related Codacy posts

      Ganesa Vijayakumar
      Ganesa Vijayakumar
      Full Stack Coder | Module Lead | 15 upvotes 505.5K views
      Codacy
      Codacy
      SonarQube
      SonarQube
      React
      React
      React Router
      React Router
      React Native
      React Native
      JavaScript
      JavaScript
      jQuery
      jQuery
      jQuery UI
      jQuery UI
      jQuery Mobile
      jQuery Mobile
      Bootstrap
      Bootstrap
      Java
      Java
      Node.js
      Node.js
      MySQL
      MySQL
      Hibernate
      Hibernate
      Heroku
      Heroku
      Amazon S3
      Amazon S3
      Amazon RDS
      Amazon RDS
      Solr
      Solr
      Elasticsearch
      Elasticsearch
      Amazon Route 53
      Amazon Route 53
      Microsoft Azure
      Microsoft Azure
      Amazon EC2 Container Service
      Amazon EC2 Container Service
      Apache Maven
      Apache Maven
      Git
      Git
      Docker
      Docker

      I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

      I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

      As per my work experience and knowledge, I have chosen the followings stacks to this mission.

      UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

      Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

      Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

      Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

      Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

      Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

      Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

      Happy Coding! Suggestions are welcome! :)

      Thanks, Ganesa

      See more
      SonarQube
      SonarQube
      codebeat
      codebeat
      Codacy
      Codacy

      It is very important to have clean code. To be sure that the code quality is not really bad I use a few tools. I love SonarQube with many relevant hints and deep analysis of code. codebeat isn't so detailed, but it can find complexity issues and duplications. Codacy cannot find more bugs then your IDE. The winner for me is SonarQube that shows me really relevant bugs in my code.

      See more
      FindBugs logo

      FindBugs

      18
      8
      0
      18
      8
      + 1
      0
      An open-source static code analyser
        Be the first to leave a pro
        FindBugs logo
        FindBugs
        VS
        SonarQube logo
        SonarQube

        related FindBugs posts

        Joshua Dean K眉pper
        Joshua Dean K眉pper
        CEO at Scrayos UG (haftungsbeschr盲nkt) | 1 upvotes 11.6K views
        atScrayos UG (haftungsbeschr盲nkt)Scrayos UG (haftungsbeschr盲nkt)
        Checkstyle
        Checkstyle
        FindBugs
        FindBugs

        We use PMD alongside Checkstyle and FindBugs (Spotbugs) for our static code analysis, as a standard stage in all of our pipelines. PMD offers us insight into various optimization possibilities, best-practice alignment, coding convention compliance and general problems with our code.

        See more

        related ESLint posts

        Johnny Bell
        Johnny Bell
        Senior Software Engineer at StackShare | 17 upvotes 149.9K views
        Webpack
        Webpack
        Node.js
        Node.js
        Yarn
        Yarn
        npm
        npm
        Babel
        Babel
        Prettier
        Prettier
        ESLint
        ESLint
        #ES6
        #ES5

        So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

        So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

        The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

        I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

        Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

        I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

        See more
        Francisco Quintero
        Francisco Quintero
        Tech Lead at Dev As Pros | 7 upvotes 80.3K views
        atDev As ProsDev As Pros
        Node.js
        Node.js
        Rails
        Rails
        Amazon EC2
        Amazon EC2
        Heroku
        Heroku
        RuboCop
        RuboCop
        JavaScript
        JavaScript
        ESLint
        ESLint
        Slack
        Slack
        Twist
        Twist

        For many(if not all) small and medium size business time and cost matter a lot.

        That's why languages, frameworks, tools, and services that are easy to use and provide 0 to productive in less time, it's best.

        Maybe Node.js frameworks might provide better features compared to Rails but in terms of MVPs, for us Rails is the leading alternative.

        Amazon EC2 might be cheaper and more customizable than Heroku but in the initial terms of a project, you need to complete configurationos and deploy early.

        Advanced configurations can be done down the road, when the project is running and making money, not before.

        But moving fast isn't the only thing we care about. We also take the job to leave a good codebase from the beginning and because of that we try to follow, as much as we can, style guides in Ruby with RuboCop and in JavaScript with ESLint and StandardJS.

        Finally, comunication and keeping a good history of conversations, decisions, and discussions is important so we use a mix of Slack and Twist

        See more

        related Code Climate posts

        Jerome Dalbert
        Jerome Dalbert
        Senior Backend Engineer at StackShare | 5 upvotes 74K views
        atStackShareStackShare
        GitHub
        GitHub
        CircleCI
        CircleCI
        Code Climate
        Code Climate
        Brakeman
        Brakeman
        RuboCop
        RuboCop
        RSpec
        RSpec
        Rails
        Rails
        Git
        Git
        #ContinuousIntegration

        The continuous integration process for our Rails backend app starts by opening a GitHub pull request. This triggers a CircleCI build and some Code Climate checks.

        The CircleCI build is a workflow that runs the following jobs:

        • check for security vulnerabilities with Brakeman
        • check code quality with RuboCop
        • run RSpec tests in parallel with the knapsack gem, and output test coverage reports with the simplecov gem
        • upload test coverage to Code Climate

        Code Climate checks the following:

        • code quality metrics like code complexity
        • test coverage minimum thresholds

        The CircleCI jobs and Code Climate checks above have corresponding GitHub status checks.

        Once all the mandatory GitHub checks pass and the code+functionality have been reviewed, developers can merge their pull request into our Git master branch. Code is then ready to deploy!

        #ContinuousIntegration

        See more
        Prettier logo

        Prettier

        324
        133
        0
        324
        133
        + 1
        0
        Prettier is an opinionated code formatter.
          Be the first to leave a pro
          Prettier logo
          Prettier
          VS
          SonarQube logo
          SonarQube

          related Prettier posts

          Johnny Bell
          Johnny Bell
          Senior Software Engineer at StackShare | 17 upvotes 149.9K views
          Webpack
          Webpack
          Node.js
          Node.js
          Yarn
          Yarn
          npm
          npm
          Babel
          Babel
          Prettier
          Prettier
          ESLint
          ESLint
          #ES6
          #ES5

          So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

          So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

          The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

          I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

          Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

          I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

          See more
          Russel Werner
          Russel Werner
          Lead Engineer at StackShare | 7 upvotes 58.5K views
          atStackShareStackShare
          Prettier
          Prettier
          ESLint
          ESLint
          WebStorm
          WebStorm
          Visual Studio Code
          Visual Studio Code

          We use Prettier because when we rebooted our front-end stack, I decided that it would be an efficient use of our time to not worry about code formatting issues and personal preferences during peer review. Prettier eliminates this concern by auto-formatting our code to a deterministic output. We use it along with ESLint and have 1st-class support in our WebStorm and Visual Studio Code editors.

          See more

          related RuboCop posts

          Francisco Quintero
          Francisco Quintero
          Tech Lead at Dev As Pros | 7 upvotes 80.3K views
          atDev As ProsDev As Pros
          Node.js
          Node.js
          Rails
          Rails
          Amazon EC2
          Amazon EC2
          Heroku
          Heroku
          RuboCop
          RuboCop
          JavaScript
          JavaScript
          ESLint
          ESLint
          Slack
          Slack
          Twist
          Twist

          For many(if not all) small and medium size business time and cost matter a lot.

          That's why languages, frameworks, tools, and services that are easy to use and provide 0 to productive in less time, it's best.

          Maybe Node.js frameworks might provide better features compared to Rails but in terms of MVPs, for us Rails is the leading alternative.

          Amazon EC2 might be cheaper and more customizable than Heroku but in the initial terms of a project, you need to complete configurationos and deploy early.

          Advanced configurations can be done down the road, when the project is running and making money, not before.

          But moving fast isn't the only thing we care about. We also take the job to leave a good codebase from the beginning and because of that we try to follow, as much as we can, style guides in Ruby with RuboCop and in JavaScript with ESLint and StandardJS.

          Finally, comunication and keeping a good history of conversations, decisions, and discussions is important so we use a mix of Slack and Twist

          See more
          Jerome Dalbert
          Jerome Dalbert
          Senior Backend Engineer at StackShare | 5 upvotes 74K views
          atStackShareStackShare
          GitHub
          GitHub
          CircleCI
          CircleCI
          Code Climate
          Code Climate
          Brakeman
          Brakeman
          RuboCop
          RuboCop
          RSpec
          RSpec
          Rails
          Rails
          Git
          Git
          #ContinuousIntegration

          The continuous integration process for our Rails backend app starts by opening a GitHub pull request. This triggers a CircleCI build and some Code Climate checks.

          The CircleCI build is a workflow that runs the following jobs:

          • check for security vulnerabilities with Brakeman
          • check code quality with RuboCop
          • run RSpec tests in parallel with the knapsack gem, and output test coverage reports with the simplecov gem
          • upload test coverage to Code Climate

          Code Climate checks the following:

          • code quality metrics like code complexity
          • test coverage minimum thresholds

          The CircleCI jobs and Code Climate checks above have corresponding GitHub status checks.

          Once all the mandatory GitHub checks pass and the code+functionality have been reviewed, developers can merge their pull request into our Git master branch. Code is then ready to deploy!

          #ContinuousIntegration

          See more
          TSLint logo

          TSLint

          117
          39
          0
          117
          39
          + 1
          0
          An extensible linter for the TypeScript language
            Be the first to leave a pro
            TSLint logo
            TSLint
            VS
            SonarQube logo
            SonarQube

            related TSLint posts

            Forrest Norvell
            Forrest Norvell
            engineering manager at self-employed | 6 upvotes 31.1K views
            TSLint
            TSLint
            ESLint
            ESLint
            Flow (JS)
            Flow (JS)
            Visual Studio Code
            Visual Studio Code
            TypeScript
            TypeScript

            I use TypeScript because the tooling is more mature (the decision to discontinue TSLint in favor of moving all its checks to ESLint is a thoughtful and mature decision), there's a ton of examples and tutorials for it, and it just generally seems to be where the industry is headed. Flow (JS) is a fine tool, but it just hasn't seen the uptake that TS has, and as a result is lacking a lot of the nicer small things, like thorough Visual Studio Code integration, offered by TS.

            See more
            Stylelint logo

            Stylelint

            90
            28
            1
            90
            28
            + 1
            1
            A mighty, modern CSS linter
            Stylelint logo
            Stylelint
            VS
            SonarQube logo
            SonarQube

            related Stylelint posts

            Zarema Khalilova
            Zarema Khalilova
            Frontend Team Lead at Uploadcare | 3 upvotes 29.1K views
            atUploadcareUploadcare
            ESLint
            ESLint
            Stylelint
            Stylelint
            #JavaScript
            #Markdown

            To avoid code formatting conflicts and keep a high quality of code we use linters. ESLint for #JavaScript, Stylelint for #CSS, remark-lint for #markdown. Good point that tools allow using shareable config, it useful cause we have many projects.

            See more
            Snyk logo

            Snyk

            78
            51
            0
            78
            51
            + 1
            0
            Fix vulnerabilities in Node & npm dependencies with a click
              Be the first to leave a pro
              Snyk logo
              Snyk
              VS
              SonarQube logo
              SonarQube
              Crucible logo

              Crucible

              33
              26
              10
              33
              26
              + 1
              10
              Review code, discuss changes, share knowledge, and identify defects
              Crucible logo
              Crucible
              VS
              SonarQube logo
              SonarQube
              Standard JS logo

              Standard JS

              32
              9
              0
              32
              9
              + 1
              0
              A JavaScript Standard Style
                Be the first to leave a pro
                Standard JS logo
                Standard JS
                VS
                SonarQube logo
                SonarQube
                Hound logo

                Hound

                30
                30