Infer
fbinfer.com
- Free plan
- macOS
- Linux
- Web
- Self-hosted
What Infer is
Infer is a static analysis tool that examines compiled Java, C, C++, Objective-C, and Erlang code and reports potential bugs before release. Its checks cover issues such as null pointer errors, memory or resource leaks, unavailable APIs, coding conventions, and concurrency problems. Some analyses can trace a problem across functions or methods in different files. Pulse focuses on memory safety and value analysis, while RacerD checks thread safety. Infer captures build commands, analyzes the files included in that capture, and creates reports that can be explored with infer explore; files not compiled are not analyzed. Documented build integrations include ant, Buck, CMake, Gradle, Make, Maven, xcodebuild, and xctool. It can be installed from a binary release, built from source, or run in Docker, and a small browser example is available through Codeboard. Infer supports Linux and macOS, not Windows. It is free, with a listed price of free.
Who it suits
Infer suits development teams that want automated checks for Java or C-family code in their build and CI workflows. Teams need a supported Linux or macOS environment and must compile files for them to be analyzed.
Good to know, and what to watch
- Checks for null dereferences, leaks, and concurrency issues
- Can reason across multiple functions and files
- Integrates with several documented build systems
- Free plan listed as free
- Offers binary, source-build, Docker, and browser options
- Not supported on Windows
- Uncompiled files are not analyzed
- Cost analysis does not support Python, Rust, or Swift
Plans
Every plan and priceInfer (free)
Free plan
Getting started
- Open the Infer website
- Choose a binary release, source build, or Docker image
- Integrate Infer with a supported build system or compilation database
- Capture compilation commands for the files to analyze
- Run analysis and inspect reports with infer explore
- Try the browser example through Codeboard
Limits to check
Infer analyzes only files captured during compilation, so uncompiled files receive no analysis. The latest binary release supports Linux and macOS, not Windows; cost analysis also has the listed language limits.
The Club's review
Overview
Infer is a free static analyzer for Java, C, C++, Objective-C and Erlang, aimed at developers who want potential bugs identified before code ships. Its cross-file analysis is a strong fit for supported projects with established build workflows; teams on Windows or with builds that do not compile every relevant file should look elsewhere.
Key features
Infer captures compilation commands, analyzes the captured files and produces reports for review with infer explore. That approach can fit into an existing build, but it draws a firm boundary around analysis: files not compiled are not analyzed. For continuous integration, the recommended workflow identifies modified files and runs reactive analysis starting from them.
Checks vary by language. For Java and Android, Infer targets null-pointer exceptions, resource leaks, annotation reachability, missing lock guards and concurrency races. For C, C++ and Objective-C, it checks null dereferences, memory leaks, coding conventions and unavailable APIs. Its ability to reason across functions or methods in different files makes it useful for defects that depend on interactions beyond one local expression.
Pulse provides interprocedural memory-safety analysis, including Java null-dereference detection, while RacerD focuses on thread safety. Cost analysis estimates asymptotic function complexity for Java and C-family languages. Hack support is experimental; Python, Rust and Swift are not supported by cost analysis.
Documented build integrations include ant, Buck, CMake, Gradle, Make, Maven, xcodebuild and xctool, as well as compilation databases. Infer can be installed from binary releases, built from source or run in Docker. A small browser example is also available through Codeboard, a useful way to try the tool before setting up a local build.
Pricing
Infer is free: its plan costs nothing and includes static analysis for supported programming languages, with a downloadable binary, source build or Docker image. That removes a software fee, but the value depends on whether a project fits the supported systems and capture-based workflow. Teams should also account for the license caveat: the repository is MIT-licensed, while enabling Java support may require GPL-licensed components.
Platforms
Infer supports Linux and macOS, and can be run self-hosted or through its browser demo. It is not supported on Windows; the documentation suggests a Linux virtual machine if the project can compile there. That makes operating-system compatibility a central selection check, not a minor installation detail.
Who it's for
Infer suits development teams maintaining Java or C-family code that can capture builds and wants static checks in an existing CI pipeline. Meta uses it in continuous integration to verify selected properties of code changes across projects including Facebook, Messenger, Instagram and WhatsApp. That demonstrates a fit for CI use, though it does not remove the need to confirm that a team's own build captures the files it needs analyzed.
It is a weaker fit for Windows-only teams, projects whose relevant files are not compiled in the captured workflow, or users seeking cost analysis for Python, Rust or Swift. Support is provided through GitHub issues and the #infer IRC channel on Libera Chat.
Pros and cons
- Pros: Cross-function and cross-file reasoning can catch bugs that depend on interactions across a codebase, including null dereferences and data races.
- Pros: A free plan, multiple installation routes and integrations with common build systems give teams several ways to incorporate analysis.
- Cons: Analysis covers only files captured during compilation, so uncompiled files remain unchecked.
- Cons: Windows is unsupported, and Java support may require GPL-licensed components despite the repository's MIT license.
- Cons: Cost analysis has language limits, and Hack support is experimental.
Alternatives
For C and C++-specific options, browse C and C++ Static Analysis Tools; for a broader comparison, see Static Analysis Tools.
- Qodana is worth considering for teams that want a freemium option with a free trial and support for Windows as well as Linux, macOS, self-hosted and web environments.
- MATLAB Grader is a free alternative for users with a MATLAB license current under maintenance; LMS integration requires a qualifying academic license.
- Parasoft SOAtest is a paid option with a free trial and tailored pricing for business needs.
- Semgrep Code offers a free edition with Code and Supply Chain for up to 10 repositories and 10 contributors, plus 60 AI credits; its platform support includes Windows.
- Squish is a paid alternative with a free trial and broad platform support, including Windows and mobile platforms.
- CBMC is a free, command-line alternative for Linux, macOS and Windows under a BSD 4-clause license.
- LDRA Tool Suite is a paid alternative with a free trial and Linux, macOS, self-hosted and Windows support.
- PVS-Studio offers paid plans, a free plan and a free trial, with Linux, macOS and Windows support.
Verdict
Choose Infer if your Java or C-family project builds on Linux or macOS and you want free, cross-file static analysis that can join an existing build and CI process. Its main advantage is analysis that can follow bugs across functions; its main reasons to look elsewhere are the Windows exclusion and the requirement that files be captured during compilation.
The verdict
Infer offers a broad set of static checks for supported codebases and can fit into existing build workflows. Its platform limitation and dependence on captured compilation make those requirements important to assess first.
Questions people ask
How much does Infer cost?
The Infer free plan is free.
Which languages does Infer support?
Its documented language support includes Java, C, C++, Objective-C, and Erlang.
Which platforms can run Infer?
Infer provides binary releases for Linux and macOS, and it can also be built from source or run in Docker.
Can Infer run in CI/CD?
Yes. Infer is used in Meta’s continuous-integration pipeline and supports CI workflows.
Which build systems integrate with Infer?
Documented integrations include ant, Buck, CMake, Gradle, Make, Maven, xcodebuild, xctool, and compilation databases.
What the maker publishes
- Analysis workflow
- Infer captures compilation commands, analyzes the captured files, and writes reports that can be explored with infer explore. source
- Browser demo
- Infer can be tried on a small example in a browser through Codeboard. source
- Bug detection
- Infer can detect issues including null pointer dereferences, data races, and other bugs that may span multiple functions or files. source
- Build integrations
- Documented build system integrations include ant, Buck, CMake, Gradle, Make, Maven, xcodebuild, and xctool. source
- C-family checks
- For C, C++, and iOS/Objective-C, Infer checks null pointer dereferences, memory leaks, coding conventions, and unavailable APIs. source
- Checker features
- Available checkers include Pulse for general-purpose memory and value analysis and RacerD for thread-safety analysis. source
- CI use
- The recommended CI flow is to identify modified files and run analysis in reactive mode starting from those files. source
- Cost analysis
- Cost analysis computes asymptotic function complexity and supports C/C++/Objective-C and Java, with Hack experimental and no Python, Rust, or Swift support. source
- Deep analysis
- Infer can detect issues such as null pointer dereferences and data races by reasoning across multiple functions or methods in different files. source
- Deployment
- Infer runs in Meta's continuous-integration pipeline to verify select properties of code modifications for projects including Facebook, Messenger, Instagram, and WhatsApp. source
- Download options
- Users can download binary releases, build Infer from source, or use a Docker image; the getting-started guide also offers a small browser example through Codeboard. source
- Installation
- Infer can be installed from binary releases, built from source, or run using Docker images. source
- Integrations
- Infer documents integrations for Buck, cmake, Gradle, Make, Maven, Xcodebuild, xctool, and compilation databases. source
- Java checks
- For Android and Java, Infer checks null pointer exceptions, resource leaks, annotation reachability, missing lock guards, and concurrency race conditions. source
- Languages
- The documentation lists Java, C, C++, Objective-C, and Erlang; the latest release notes also describe Python and Swift frontends and an experimental Rust frontend. source
- License
- The Infer repository states that Infer is MIT-licensed, while noting that enabling Java support may require GPL-licensed components. source
- Limit
- Infer analyzes files captured during compilation, so if no file is compiled, no file is analyzed. source
- Maker use
- Infer is deployed within Meta's continuous integration pipeline to verify selected properties of code modifications across projects including Facebook, Messenger, Instagram, and WhatsApp. source
- Pulse
- Pulse is an interprocedural memory safety analysis that can detect null dereferences in Java. source
- Purpose
- Infer is a static analysis tool that produces a list of potential bugs from Java or C/C++/Objective-C code. source
- Support
- Support is provided through GitHub issues and the #infer IRC channel on Libera Chat. source
- Support
- The project directs users to GitHub issues and the #infer IRC channel on Libera Chat for questions and issue reports. source
- Supported languages
- Infer is a static program analyzer for Java, C, C++, Objective-C, and Erlang, written in OCaml. source
- Supported systems
- The latest release is described as a binary release for Linux and macOS, while the support FAQ says Infer is not supported on Windows. source
Checked against the maker's pages on 2 Oct 2026.