CodeChecker vs Infer

CodeChecker is free, open-source static-analysis infrastructure built on LLVM and Clang Static Analyzer tooling. Its command-line tools run supported analyzers against a JSON compilation database and generate reports. The web interface stores, filters, compares, and visualizes findings, including code bug paths, while reviewers can comment and set status. Reanalysis can be limited to changed files and their dependencies. Listed language coverage includes C/C++, C#, Java, Python, JavaScript, TypeScript, Go, and Markdown. Integrations cover Gerrit, GitLab, and a reusable GitHub Actions workflow. A Visual Studio Code extension runs analysis, reanalyzes saved files, and browses reports. Servers can run locally or in Docker, with PostgreSQL or SQLite storage and configurable authentication. CodeChecker requires Python 3.11 or later.

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 include null pointer problems, resource or memory leaks, coding conventions, unavailable APIs, and concurrency issues such as data races. Some analyses can follow an issue across multiple functions or methods and files. Pulse provides memory-safety analysis, while RacerD checks 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 that analysis. Infer captures compilation commands, analyzes the captured files, and writes reports that can be reviewed with `infer explore`; files that are not compiled are not analyzed. Integrations are documented for build tools including Buck, CMake, Gradle, Make, Maven, Xcodebuild, and xctool. It can be installed from binary releases, built from source, or run in Docker. The free plan costs nothing. Infer runs on Linux and macOS, with web and self-hosted options; Windows is not supported.