Infer

Overview

Infer is a free static analyzer for teams that want potential bugs surfaced before code ships, particularly in Java and C-family projects. Its ability to reason across files is a meaningful advantage for bugs that local checks can miss, provided the build and platform fit its capture-based workflow.

Key features

Infer records compilation commands, analyzes the files included in that compilation, and produces reports developers can explore with infer explore. This connects analysis to existing builds, but leaves a clear blind spot: a file that is not compiled is not analyzed. For CI, the recommended approach is to identify changed files and run reactive analysis from them.

Checks cover different concerns by language. For Java and Android, Infer looks for null-pointer exceptions, resource leaks, annotation reachability issues, missing lock guards, and concurrency races. For C, C++, and Objective-C, it checks for null dereferences, memory leaks, coding-convention issues, and unavailable APIs. Its cross-function and cross-file reasoning is useful when a bug depends on how separate methods interact, rather than on one isolated line.

Pulse provides interprocedural memory-safety and value analysis, including Java null-dereference detection; RacerD focuses on thread safety. Cost analysis estimates asymptotic function complexity for Java and C-family languages. Hack support is experimental, and Python, Rust, and Swift are not supported by cost analysis.

Documented build integrations include ant, Buck, CMake, Gradle, Make, Maven, xcodebuild, xctool, and compilation databases. Users can install a binary release, build from source, or use Docker; a small browser example is also available through Codeboard. Infer is used in Meta's CI pipeline to verify selected properties of code changes across projects including Facebook, Messenger, Instagram, and WhatsApp, evidence of deployment at scale rather than a guarantee for every project.

Pricing

Infer (free): free. The free plan provides static analysis for supported programming languages, with a downloadable binary, source build, or Docker image. There are no paid tiers or seat and quota terms to weigh in this plan.

The repository is MIT-licensed, though enabling Java support may require GPL-licensed components. Teams evaluating licensing should account for that distinction, especially when distributing or embedding tooling.

Platforms

Infer supports Linux and macOS releases and can be self-hosted; a browser example offers a limited way to try it online. Windows is not supported. The suggested workaround is a Linux virtual machine, which is viable only if the project itself can compile on Linux. This makes Infer a poor fit for Windows-only build environments.

Who it's for

Infer is best suited to engineering teams with Java or C-family code, builds that can run on Linux or macOS, and CI workflows where compilation capture can be maintained. Its cross-file analysis and range of build integrations make it attractive for teams targeting correctness and safety issues without adopting a paid plan. It is less suitable when Windows is mandatory, when important files are not compiled in the analyzed workflow, or when the required language falls outside its supported set.

Pros and cons

Pros

• Cross-file reasoning: can find issues such as null dereferences and data races that span multiple functions or files.
• Broad build integration: documented support for common build systems and compilation databases can fit established workflows.
• Free deployment choices: binary, source, and Docker options allow teams to choose how to run it without a subscription.

Cons

• Compilation-dependent coverage: files not compiled during capture are not analyzed, so coverage depends on the build workflow.
• No Windows support: Windows-only teams must change environments, and the Linux VM option depends on Linux compilation.
• Language caveats: cost analysis has narrower language support, while Hack support is experimental.
• Java licensing qualification: Java support may involve GPL-licensed components despite the repository's MIT license.

Alternatives

Static Analysis Tools and C and C++ Static Analysis Tools are useful starting points for comparing options by category.

Choose PMD for a free downloadable static analyzer with a BSD-style license, or Clang Static Analyzer for an open-source analyzer focused on C, C++, and Objective-C. Cppcheck is another option for free core static analysis, with a paid Project plan also offered.

MATLAB Grader is free with a current MATLAB maintenance license; LMS integration requires a qualifying academic license. Qodana offers a Community plan with a free tier and trial, while Semgrep Code has a Free Edition capped at 10 repositories and 10 contributors, with 60 AI credits. Snyk Open Source is a closer alternative for software-composition analysis, with its free plan limited to five projects. CodeScene may suit open-source projects seeking its free Community Edition features, including automated PR reviews, hotspots, and knowledge distribution.

Verdict

Choose Infer if you need free, cross-file static analysis for supported Java or C-family code and can build on Linux or macOS. Its strongest case is reasoning across functions within an existing CI and compilation workflow. Look elsewhere if Windows is essential, your target files are not compiled in the analysis path, or your language and analysis needs exceed its supported scope.