Infer vs SonarQube

Overview

SonarQube

Stacks1.9K

Followers2.0K

Votes53

GitHub Stars10.0K

Forks2.1K

Infer

Stacks18

Followers69

Votes0

GitHub Stars15.4K

Forks2.1K

Infer vs SonarQube: What are the differences?

Key Differences between Infer and SonarQube

Analysis Technique: Infer and SonarQube employ different analysis techniques to identify code quality issues. Infer is a static analysis tool that uses a combination of abstract interpretation and symbolic execution to detect bugs and vulnerabilities. On the other hand, SonarQube utilizes a rule-based approach, where it compares code against a set of predefined rules to identify issues.
Supported Languages: Another significant difference is the set of supported languages. Infer primarily focuses on providing analysis for C, C++, and Objective-C code. In contrast, SonarQube supports a wide range of languages, including Java, C#, JavaScript, Python, and many more.
Integration and CI/CD Support: Both Infer and SonarQube offer integration options with build systems and CI/CD pipelines. However, the approach differs to some extent. Infer can easily integrate with build systems like Gradle, Buck, and Maven, allowing analysis during the build process. SonarQube provides plugins for popular build tools like Maven and Gradle, enabling seamless integration with CI/CD pipelines.
Developer-Friendly Tool: Infer focuses on providing developers with fast feedback during the development process, aiming to catch defects before they surface in code reviews or testing. It provides actionable reports by identifying the exact location of bugs and vulnerabilities. SonarQube, on the other hand, offers a more comprehensive analysis of various code quality aspects, along with reporting and visualization features for code maintainability and technical debt.
Cost and Licensing: The two tools also differ in terms of cost and licensing. Infer is an open-source tool released under the MIT license, making it free to use and modify. SonarQube comes in both open-source and commercial editions, with the commercial editions offering additional features and support that come at a cost.

In summary, Infer stands out with its advanced static analysis techniques, focused language support, and developer-centric features, while SonarQube offers a broader language support, comprehensive code quality analysis, and customizable reporting capabilities.

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

Detailed Comparison

SonarQube	Infer
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.
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 Forks 2.1K	GitHub Forks 2.1K
Stacks 1.9K	Stacks 18
Followers 2.0K	Followers 69
Votes 53	Votes 0
Pros & Cons
Pros 26 Tracks code complexity and smell trends 16 IDE Integration 9 Complete code Review 2 Difficult to deploy Cons 7 Sales process is long and unfriendly 7 Paid support is poor, techs arrogant and unhelpful 1 Does not integrate with Snyk	No community feedback yet
Integrations
Gradle Apache Maven Jenkins TeamCity Appveyor Travis CI Apache Ant Bamboo	Cocoa Touch (iOS) Android SDK Java Objective-C

What are some alternatives to SonarQube, Infer?

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.

ESLint

A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

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.

Related Comparisons

Infer vs SonarQube: What are the differences?

Key Differences between Infer and SonarQube

Analysis Technique: Infer and SonarQube employ different analysis techniques to identify code quality issues. Infer is a static analysis tool that uses a combination of abstract interpretation and symbolic execution to detect bugs and vulnerabilities. On the other hand, SonarQube utilizes a rule-based approach, where it compares code against a set of predefined rules to identify issues.
Supported Languages: Another significant difference is the set of supported languages. Infer primarily focuses on providing analysis for C, C++, and Objective-C code. In contrast, SonarQube supports a wide range of languages, including Java, C#, JavaScript, Python, and many more.
Integration and CI/CD Support: Both Infer and SonarQube offer integration options with build systems and CI/CD pipelines. However, the approach differs to some extent. Infer can easily integrate with build systems like Gradle, Buck, and Maven, allowing analysis during the build process. SonarQube provides plugins for popular build tools like Maven and Gradle, enabling seamless integration with CI/CD pipelines.
Developer-Friendly Tool: Infer focuses on providing developers with fast feedback during the development process, aiming to catch defects before they surface in code reviews or testing. It provides actionable reports by identifying the exact location of bugs and vulnerabilities. SonarQube, on the other hand, offers a more comprehensive analysis of various code quality aspects, along with reporting and visualization features for code maintainability and technical debt.
Cost and Licensing: The two tools also differ in terms of cost and licensing. Infer is an open-source tool released under the MIT license, making it free to use and modify. SonarQube comes in both open-source and commercial editions, with the commercial editions offering additional features and support that come at a cost.

Infer vs SonarQube

Overview

Infer vs SonarQube: What are the differences?