Alternatives to SonarLint logo

Alternatives to SonarLint

ReSharper, SonarQube, FindBugs, PMD, and JSLint are the most popular alternatives and competitors to SonarLint.
43
80
+ 1
3

What is SonarLint and what are its top alternatives?

It is an IDE extension that helps you detect and fix quality issues as you write code. Like a spell checker, it squiggles flaws so that they can be fixed before committing code.
SonarLint is a tool in the Code Review category of a tech stack.

Top Alternatives of SonarLint

SonarLint alternatives & related posts

ReSharper logo

ReSharper

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

    SonarQube

    769
    683
    19
    769
    683
    + 1
    19
    Continuous Code Quality
    SonarQube logo
    SonarQube
    VS
    SonarLint logo
    SonarLint

    related SonarQube posts

    Simon Reymann
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH | 22 upvotes 135.9K views

    Our whole DevOps stack consists of the following tools:

    • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
    • Respectively Git as revision control system
    • SourceTree as Git GUI
    • Visual Studio Code as IDE
    • CircleCI for continuous integration (automatize development process)
    • Prettier / TSLint / ESLint as code linter
    • SonarQube as quality gate
    • Docker as container management (incl. Docker Compose for multi-container application management)
    • VirtualBox for operating system simulation tests
    • Kubernetes as cluster management for docker containers
    • Heroku for deploying in test environments
    • nginx as web server (preferably used as facade server in production environment)
    • SSLMate (using OpenSSL) for certificate management
    • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
    • PostgreSQL as preferred database system
    • Redis as preferred in-memory database/store (great for caching)

    The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

    • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
    • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
    • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
    • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
    • Scalability: All-in-one framework for distributed systems.
    • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
    See more
    Ganesa Vijayakumar
    Ganesa Vijayakumar
    Full Stack Coder | Module Lead | 15 upvotes 1.3M views

    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
    FindBugs logo

    FindBugs

    29
    36
    0
    29
    36
    + 1
    0
    An open-source static code analyser
      Be the first to leave a pro
      FindBugs logo
      FindBugs
      VS
      SonarLint logo
      SonarLint

      related FindBugs posts

      Joshua Dean K眉pper
      Joshua Dean K眉pper
      CEO at Scrayos UG (haftungsbeschr盲nkt) | 1 upvotes 183.8K views

      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
      PMD logo

      PMD

      15
      19
      0
      15
      19
      + 1
      0
      An extensible cross-language static code analyzer
        Be the first to leave a pro
        PMD logo
        PMD
        VS
        SonarLint logo
        SonarLint

        related PMD posts

        Joshua Dean K眉pper
        Joshua Dean K眉pper
        CEO at Scrayos UG (haftungsbeschr盲nkt) | 1 upvotes 183.8K views

        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
        JSLint logo

        JSLint

        7
        4
        0
        7
        4
        + 1
        0
        A Code Quality Tool for Javascript
          Be the first to leave a pro
          JSLint logo
          JSLint
          VS
          SonarLint logo
          SonarLint
          ESLint logo

          ESLint

          6.5K
          4.5K
          17
          6.5K
          4.5K
          + 1
          17
          The fully pluggable JavaScript code quality tool
          ESLint logo
          ESLint
          VS
          SonarLint logo
          SonarLint

          related ESLint posts

          Simon Reymann
          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH | 22 upvotes 135.9K views

          Our whole DevOps stack consists of the following tools:

          • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
          • Respectively Git as revision control system
          • SourceTree as Git GUI
          • Visual Studio Code as IDE
          • CircleCI for continuous integration (automatize development process)
          • Prettier / TSLint / ESLint as code linter
          • SonarQube as quality gate
          • Docker as container management (incl. Docker Compose for multi-container application management)
          • VirtualBox for operating system simulation tests
          • Kubernetes as cluster management for docker containers
          • Heroku for deploying in test environments
          • nginx as web server (preferably used as facade server in production environment)
          • SSLMate (using OpenSSL) for certificate management
          • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
          • PostgreSQL as preferred database system
          • Redis as preferred in-memory database/store (great for caching)

          The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

          • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
          • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
          • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
          • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
          • Scalability: All-in-one framework for distributed systems.
          • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
          See more
          Johnny Bell
          Johnny Bell
          Senior Software Engineer at StackShare | 17 upvotes 801.4K views

          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
          Pylint logo

          Pylint

          38
          28
          0
          38
          28
          + 1
          0
          Source-code, bug and quality checker for the Python programming language
            Be the first to leave a pro
            Pylint logo
            Pylint
            VS
            SonarLint logo
            SonarLint
            Checkstyle  logo

            Checkstyle

            43
            43
            0
            43
            43
            + 1
            0
            A static code analysis tool
              Be the first to leave a pro
              Checkstyle  logo
              Checkstyle
              VS
              SonarLint logo
              SonarLint

              related Checkstyle posts

              Joshua Dean K眉pper
              Joshua Dean K眉pper
              CEO at Scrayos UG (haftungsbeschr盲nkt) | 10 upvotes 30.2K views

              We use Checkstyle for all of our Java projects to perform the linting. The setup was very easy and there are amazing integrations into all IDEs. What also came in very handy was that we could start off with just a basic set of rules and tighten the linting-rules step-by-step, continously improving the readability and uniformity of our codebase.

              See more
              Joshua Dean K眉pper
              Joshua Dean K眉pper
              CEO at Scrayos UG (haftungsbeschr盲nkt) | 1 upvotes 183.8K views

              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