ESLint vs Infer vs SonarQube

Overview

SonarQube

Stacks1.9K

Followers2.0K

Votes53

GitHub Stars10.0K

Forks2.1K

Infer

Stacks18

Followers69

Votes0

GitHub Stars15.4K

Forks2.1K

ESLint

Stacks38.6K

Followers14.0K

Votes28

GitHub Stars26.6K

Forks4.8K

ESLint vs Infer vs SonarQube: What are the differences?

# Introduction

## Key Differences between ESLint, Infer, and SonarQube

1. **Analysis Focus**: ESLint is focused on analyzing JavaScript code for potential errors and maintaining code consistency through coding rules. Infer, on the other hand, is designed for static analysis of C, C++, and Objective-C code to identify bugs and performance issues. SonarQube offers a more diverse range of functionalities, including code quality analysis, security vulnerability detection, and continuous inspection of various programming languages.
   
2. **Integration with CI/CD**: ESLint can be easily integrated into Continuous Integration/Continuous Deployment (CI/CD) pipelines to enforce code quality standards. Infer also provides integration options with various build systems and CI tools for automated code analysis. SonarQube excels in its integration capabilities with popular CI platforms like Jenkins, Azure DevOps, and GitHub Actions for seamless code analysis and quality management within the development workflow.
   
3. **Supported Languages**: ESLint is specifically tailored for analyzing JavaScript codebases. In contrast, Infer is primarily focused on supporting C, C++, and Objective-C languages. SonarQube, being a comprehensive code analysis tool, supports a wide range of programming languages, including Java, C#, Python, PHP, and more.
   
4. **Code Coverage Analysis**: While ESLint and Infer primarily focus on static code analysis, SonarQube offers a holistic approach by including code coverage analysis to track the proportion of code exercised by automated tests. This feature helps in identifying untested code segments and improving overall code quality through effective test coverage.
   
5. **Community Support and Extensibility**: ESLint has a robust community backing, which continually contributes to the development of new rules and plugins to enhance code analysis capabilities. Infer also benefits from an active community that supports the tool's evolution and extension possibilities. Similarly, SonarQube provides a vibrant ecosystem of plugins and extensions to customize code analysis based on specific project requirements.
   
6. **Scalability and Enterprise Usage**: SonarQube stands out in terms of scalability and enterprise-grade usage with features like project portfolio management, centralized administration, and role-based access controls. ESLint and Infer are more suitable for smaller to mid-sized projects, whereas SonarQube caters to the needs of large organizations and complex codebases.

In Summary, the key differences between ESLint, Infer, and SonarQube lie in their analysis focus, integration capabilities, supported languages, code coverage analysis, community support, and scalability for enterprise usage.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on SonarQube, Infer, ESLint

Carlos

Mar 14, 2020

Needs adviceon

Prettier

ESLint

gulp

Scenario: I want to integrate Prettier in our code base which is currently using ESLint (for .js and .scss both). The project is using gulp.

It doesn't feel quite right to me to use ESLint, I wonder if it would be better to use Stylelint or Sass Lint instead.

I completed integrating ESLint + Prettier, Planning to do the same with [ Stylelint || Sasslint || EsLint] + Prettier.

And have gulp 'fix' on file save (Watcher).

Any recommendation is appreciated.

465k views465k

Comments

Alex

Software Engineer

Aug 7, 2020

Review

you don't actually have to choose between these tools as they have vastly different purposes. i think its more a matter of understanding how to use them.

while eslint and stylelint are used to notify you about code quality issues, to guide you to write better code, prettier automatically handles code formatting (without notifying me). nothing else.

prettier and eslint both officially discourage using the eslint-plugin-prettier way, as these tools actually do very different things. autofixing with linters on watch isnt a great idea either. auto-fixing should only be done intentionally. you're not alone though, as a lot of devs set this up wrong.

i encourage you to think about what problem you're trying to solve and configure accordingly.

for my teams i set it up like this:

eslint, stylelint, prettier locally installed for cli use and ide support
eslint config prettier (code formatting rules are not eslints business, so dont warn me about it)
vscode workspace config: format on save
separate npm scripts for linting, and formatting
precommit hooks (husky)

so you can easily integrate with gulp. its just js after all ;)

159k views159k

Comments

Detailed Comparison

SonarQube	Infer	ESLint
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.	Facebook Infer is a static analysis tool - if you give Infer some Objective-C, Java, or C code, it produces a list of potential bugs. Anyone can use Infer to intercept critical bugs before they have shipped to people's phones, and help prevent crashes or poor performance.	A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Multi-language;Detect tricky issues;Security analysis;Enhance your workflow	Android and Java - Infer reports null pointer exceptions and resource leaks in Android and Java code.;iOS - In addition to this, it reports memory leak problems in iOS and C code.	-
Statistics
GitHub Stars 10.0K	GitHub Stars 15.4K	GitHub Stars 26.6K
GitHub Forks 2.1K	GitHub Forks 2.1K	GitHub Forks 4.8K
Stacks 1.9K	Stacks 18	Stacks 38.6K
Followers 2.0K	Followers 69	Followers 14.0K
Votes 53	Votes 0	Votes 28
Pros & Cons
Pros 26 Tracks code complexity and smell trends 16 IDE Integration 9 Complete code Review 2 Difficult to deploy Cons 7 Paid support is poor, techs arrogant and unhelpful 7 Sales process is long and unfriendly 1 Does not integrate with Snyk	No community feedback yet	Pros 8 Consistent javascript - opinions don't matter anymore 6 Free 6 IDE Integration 4 Customizable 2 Focuses code review on quality not style
Integrations
Gradle Apache Maven Jenkins TeamCity Appveyor Travis CI Apache Ant Bamboo	Cocoa Touch (iOS) Android SDK Java Objective-C	JavaScript

What are some alternatives to SonarQube, Infer, ESLint?

Code Climate

After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots.

Codacy

Codacy automates code reviews and monitors code quality on every commit and pull request on more than 40 programming languages reporting back the impact of every commit or PR, issues concerning code style, best practices and security.

Phabricator

Phabricator is a collection of open source web applications that help software companies build better software.

PullReview

PullReview helps Ruby and Rails developers to develop new features cleanly, on-time, and with confidence by automatically reviewing their code.

Gerrit Code Review

Gerrit is a self-hosted pre-commit code review tool. It serves as a Git hosting server with option to comment incoming changes. It is highly configurable and extensible with default guarding policies, webhooks, project access control and more.

RuboCop

RuboCop is a Ruby static code analyzer. Out of the box it will enforce many of the guidelines outlined in the community Ruby Style Guide.

CodeFactor.io

CodeFactor.io automatically and continuously tracks code quality with every GitHub or BitBucket commit and pull request, helping software developers save time in code reviews and efficiently tackle technical debt.

Amazon CodeGuru

It is a machine learning service for automated code reviews and application performance recommendations. It helps you find the most expensive lines of code that hurt application performance and keep you up all night troubleshooting, then gives you specific recommendations to fix or improve your code.

Reviewable

A code review tool for GitHub pull requests inspired by Google's internal tool. Powerful diffing and workflow features wrapped in a beautiful UI, with seamless GitHub integration. Free for public repos.

bitHound

With faster deployment cycles, a hundred competing priorities and tight deadlines to juggle– your team has a lot on their plate. Uncover and focus on the critical issues impacting your team, avoid software pitfalls and ship with confidence.

Related Comparisons

ESLint vs Infer vs SonarQube: What are the differences?

# Introduction

## Key Differences between ESLint, Infer, and SonarQube

1. **Analysis Focus**: ESLint is focused on analyzing JavaScript code for potential errors and maintaining code consistency through coding rules. Infer, on the other hand, is designed for static analysis of C, C++, and Objective-C code to identify bugs and performance issues. SonarQube offers a more diverse range of functionalities, including code quality analysis, security vulnerability detection, and continuous inspection of various programming languages.
   
2. **Integration with CI/CD**: ESLint can be easily integrated into Continuous Integration/Continuous Deployment (CI/CD) pipelines to enforce code quality standards. Infer also provides integration options with various build systems and CI tools for automated code analysis. SonarQube excels in its integration capabilities with popular CI platforms like Jenkins, Azure DevOps, and GitHub Actions for seamless code analysis and quality management within the development workflow.
   
3. **Supported Languages**: ESLint is specifically tailored for analyzing JavaScript codebases. In contrast, Infer is primarily focused on supporting C, C++, and Objective-C languages. SonarQube, being a comprehensive code analysis tool, supports a wide range of programming languages, including Java, C#, Python, PHP, and more.
   
4. **Code Coverage Analysis**: While ESLint and Infer primarily focus on static code analysis, SonarQube offers a holistic approach by including code coverage analysis to track the proportion of code exercised by automated tests. This feature helps in identifying untested code segments and improving overall code quality through effective test coverage.
   
5. **Community Support and Extensibility**: ESLint has a robust community backing, which continually contributes to the development of new rules and plugins to enhance code analysis capabilities. Infer also benefits from an active community that supports the tool's evolution and extension possibilities. Similarly, SonarQube provides a vibrant ecosystem of plugins and extensions to customize code analysis based on specific project requirements.
   
6. **Scalability and Enterprise Usage**: SonarQube stands out in terms of scalability and enterprise-grade usage with features like project portfolio management, centralized administration, and role-based access controls. ESLint and Infer are more suitable for smaller to mid-sized projects, whereas SonarQube caters to the needs of large organizations and complex codebases.

ESLint vs Infer vs SonarQube

Overview