Infer vs SonarLint

Overview

Infer

Stacks18

Followers69

Votes0

GitHub Stars15.4K

Forks2.1K

SonarLint

Stacks175

Followers352

Votes16

Infer vs SonarLint: What are the differences?

Markdown is a lightweight markup language with plain text formatting syntax for websites.

Language Support: Infer primarily focuses on analyzing C, C++, Objective-C, and Java codebases, while SonarLint offers support for a wider range of languages including JavaScript, TypeScript, C#, Python, and more.
Integration with IDEs: SonarLint integrates seamlessly with popular IDEs such as Visual Studio, IntelliJ IDEA, Eclipse, and Atom, providing real-time feedback within the development environment. Infer, on the other hand, requires a separate build step and does not have as tight integration with IDEs.
Static Analysis Techniques: Infer primarily uses static analysis techniques to identify bugs, while SonarLint combines both static and behavioral analysis to provide more comprehensive feedback on code quality and security issues.
Rule Customization: SonarLint allows users to customize the ruleset according to their project requirements, enabling them to focus on specific quality metrics. Infer, on the other hand, has a fixed set of rules which cannot be modified by users.
Scalability: Infer is known for its scalability when analyzing large codebases with millions of lines of code, while SonarLint is more suitable for smaller to medium-sized projects due to its heavier integration with IDEs.
Deployment Options: Infer can be run locally on the developer's machine or integrated into the continuous integration pipeline, while SonarLint primarily operates within the IDE without the option for server-based deployment.

In Summary, Infer and SonarLint differ in their language support, integration with IDEs, static analysis techniques, rule customization, scalability, and deployment options.

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

Infer	SonarLint
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.	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.
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.	Bug detection;Instant feedback;Know what to do;Learn from your mistakes;Uncover old issues
Statistics
GitHub Stars 15.4K	GitHub Stars -
GitHub Forks 2.1K	GitHub Forks -
Stacks 18	Stacks 175
Followers 69	Followers 352
Votes 0	Votes 16
Pros & Cons
No community feedback yet	Pros 13 IDE Integration 3 Free Cons 3 Not Very User Friendly 3 Non contextual warnings
Integrations
Cocoa Touch (iOS) Android SDK Java Objective-C	Visual Studio Visual Studio Code Eclipse IntelliJ IDEA

What are some alternatives to Infer, SonarLint?

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.

SonarQube

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.

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.

Related Comparisons

Infer vs SonarLint: What are the differences?

Markdown is a lightweight markup language with plain text formatting syntax for websites.

Language Support: Infer primarily focuses on analyzing C, C++, Objective-C, and Java codebases, while SonarLint offers support for a wider range of languages including JavaScript, TypeScript, C#, Python, and more.
Integration with IDEs: SonarLint integrates seamlessly with popular IDEs such as Visual Studio, IntelliJ IDEA, Eclipse, and Atom, providing real-time feedback within the development environment. Infer, on the other hand, requires a separate build step and does not have as tight integration with IDEs.
Static Analysis Techniques: Infer primarily uses static analysis techniques to identify bugs, while SonarLint combines both static and behavioral analysis to provide more comprehensive feedback on code quality and security issues.
Rule Customization: SonarLint allows users to customize the ruleset according to their project requirements, enabling them to focus on specific quality metrics. Infer, on the other hand, has a fixed set of rules which cannot be modified by users.
Scalability: Infer is known for its scalability when analyzing large codebases with millions of lines of code, while SonarLint is more suitable for smaller to medium-sized projects due to its heavier integration with IDEs.
Deployment Options: Infer can be run locally on the developer's machine or integrated into the continuous integration pipeline, while SonarLint primarily operates within the IDE without the option for server-based deployment.

In Summary, Infer and SonarLint differ in their language support, integration with IDEs, static analysis techniques, rule customization, scalability, and deployment options.

Infer vs SonarLint

Overview