LinthelmIntroductions to linters, static analysis and code-quality tools

Static analysis · 5 tools

Top 5 formal verification and deep analysis tools for safety-critical C code

By the Linthelm editorial team · Published · Updated · Facts checked 21 November 2026 (Asia/Dhaka)

For safety-critical C developers, this shortlist opens with Frama-C, Polyspace and Infer. Frama-C and Polyspace are documented as formal-methods tools for proving the absence of runtime errors. Infer, Clang Static Analyzer and Coverity are described as static analyzers that find bugs, so they suit teams that want broader defect detection alongside or instead of proofs.

At a glance: the shortlist in order of fit for this use case
#ToolBest forKey featurePlatforms / deploymentPricingMore
1Frama-CCEA LISTFormal proof of C code, from teaching to certificationEva plug-in uses abstract interpretation to prove absence of runtime errors from C undefined behaviorsNot stated on official pagesSee vendor pricing pageOfficial site
2PolyspaceMathWorksEmbedded teams in regulated industriesExhaustive verification of C, C++ and Ada codeIDE, CI pipelines, cloud or on-premisesSee vendor pricing pageOfficial site
3InferMetaFinding bugs in C and C++ before releaseFor C and C++, checks null pointer dereferences, memory leaks and coding conventionsNot stated on official pagesSee vendor pricing pageIntroduction
4Clang Static AnalyzerLLVM ProjectTeams already using Clang and LLVMFully open sourceCommand line via scan-build; Xcode on macOS; IDEs that use ClangSee vendor pricing pageIntroduction
5CoverityBlack DuckRegulated and enterprise C and C++ codebasesAnalyzes across files and libraries without executing codeOn-premises, including air-gapped and Kubernetes; SaaS via Polaris fAST StaticSee vendor pricing pageIntroduction

1 Frama-C

By CEA LIST

Frama-C is an open-source, extensible and collaborative platform for source-code analysis of C software. It combines formal-methods-based analyzers as plug-ins.

Why it is here: It opens the list because its documentation states that most analyzers are sound and that it is meant to guarantee no bug can happen, which matches the goal of proof.

Best for
Formal proof of C code, from teaching to certification
Key features
  • Eva plug-in uses abstract interpretation to prove absence of runtime errors from C undefined behaviors
  • WP plug-in does deductive verification with weakest precondition calculus
  • ACSL specification language for functional specifications
  • E-ACSL checks annotations at runtime
  • Graphical interface to browse code, display inferred ranges and highlight dead code
Limits
WP requires you to write function contracts and annotations such as loop invariants and assertions. It relies on SMT solvers such as Alt-Ergo, CVC5 or Z3 and offers interactive proofs when automation fails. Teams should check the vendor documentation for the effort this implies.
Platforms / deployment
Not stated on official pages
Pricing
See vendor pricing page (not quoted here; facts checked 22 November 2026, Asia/Dhaka)

2 Polyspace

By MathWorks

Polyspace is a MathWorks static code analysis tool that uses formal methods to prove the absence of critical run-time errors. It also includes checkers for coding rules, security vulnerabilities and code metrics.

Why it is here: It follows Frama-C as the other formal-methods option, with documented support for safety standards and coding rules that matter to embedded C teams.

Best for
Embedded teams in regulated industries
Key features
  • Exhaustive verification of C, C++ and Ada code
  • Checks MISRA C 2012, AUTOSAR C++14 and CERT C/C++
  • Supports DO-178C, IEC 61508, ISO 26262 and ISO/SAE 21434
  • IDE and CI integration, in the cloud or on-premises
  • Polyspace Test measures coverage including decision, condition and MC/DC
Limits
The DO Qualification Kit does not prequalify tools, and qualification must be done per project. Teams with other certification needs should check the vendor documentation.
Platforms / deployment
IDE, CI pipelines, cloud or on-premises
Pricing
See vendor pricing page (not quoted here; facts checked 22 November 2026, Asia/Dhaka)

3 Infer

By Meta

Infer is a static analysis tool that produces a list of potential bugs from Java or C/C++/Objective-C code. It is a static program analyzer written in OCaml.

Why it is here: It is the first bug-finding analyzer on the list. It is documented as finding deep issues across multiple functions or files, which is why it follows the formal-methods tools.

Best for
Finding bugs in C and C++ before release
Key features
  • For C and C++, checks null pointer dereferences, memory leaks and coding conventions
  • Finds issues that require reasoning across multiple functions or files
  • Runs in Meta's Continuous Integration pipeline
  • Developed in the open
  • Also covers Java, Objective-C and Erlang
Limits
Documented as producing a list of potential bugs, not as proving their absence. Teams that need proofs of absence should check the vendor documentation.
Platforms / deployment
Not stated on official pages
Pricing
See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)

4 Clang Static Analyzer

By LLVM Project

The Clang Static Analyzer is an open-source tool that finds bugs in C, C++ and Objective-C programs. It is part of the Clang project and built on Clang and LLVM.

Why it is here: It sits after Infer as an open-source analyzer that fits into existing Clang-based toolchains and IDEs.

Best for
Teams already using Clang and LLVM
Key features
  • Fully open source
  • scan-build command-line tool bundled in official releases
  • Can be invoked from Xcode on macOS
  • Runs alongside clang-tidy when clang-analyzer checks are enabled
  • Analysis engine is a reusable Clang library
Limits
The documentation says analysis can be much slower than compilation, and that the analyzer can report false positives. It describes finding bugs, not proving their absence.
Platforms / deployment
Command line via scan-build; Xcode on macOS; IDEs that use Clang
Pricing
See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)

5 Coverity

By Black Duck

Coverity is Black Duck's enterprise static analysis (SAST) solution. It finds security vulnerabilities and code quality defects in source code without executing it.

Why it is here: It closes the list as an enterprise analyzer with documented certification and qualification material for safety-critical C and C++ projects.

Best for
Regulated and enterprise C and C++ codebases
Key features
  • Analyzes across files and libraries without executing code
  • Supports MISRA C, AUTOSAR C++14, CERT and ISO 26262
  • Certified by TÜV SÜD under IEC 61508-3 and qualified up to ASIL D and DO-178C Level A
  • Qualification Kit supports configuration for safety-critical projects
  • Fully air-gapped on-premises deployment, or SaaS via Polaris fAST Static
Limits
Documented as static analysis for finding defects and vulnerabilities, not as formal proof of their absence. Teams that need proofs should check the vendor documentation.
Platforms / deployment
On-premises, including air-gapped and Kubernetes; SaaS via Polaris fAST Static
Pricing
See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)

How we chose these tools

We looked at how well each tool fits the job of proving the absence of runtime errors and verifying C code formally. That meant the verification techniques the vendor documents, the standards and coding rules it supports, and how it deploys, whether in an IDE, in CI or on-premises. Tools whose documentation describes formal or sound analysis come first. Tools documented as bug-finding static analyzers follow.

Every fact comes from official vendor pages and is recorded with a check date. The order reflects editorial fit for this use case, explained in the "why here" line of each entry, and does not claim that any tool is better overall. The list is built from documentation, not product trials, so it describes what each vendor documents and not how the tool behaves on your code.

Order used in this guide: Ordered by rigor of verification, with formal-methods tools first and heuristic analyzers after.

Frequently asked questions

Which tools on this list are documented as proving the absence of runtime errors?

Frama-C documents its Eva plug-in as aiming to prove the absence of runtime errors caused by C undefined behaviors. Polyspace documents formal methods to prove the absence of critical run-time errors.

What is the difference between Frama-C Eva and WP?

Eva uses abstract interpretation for a sound analysis of the entire program. WP does deductive verification of functional correctness and needs function contracts and annotations such as loop invariants.

Which tools support MISRA C?

Polyspace checks MISRA C 2012, and Coverity supports MISRA C. The other three tools do not list MISRA C support on the pages we used.

Can these tools run in CI pipelines?

Polyspace documents CI integration and server products for continuous verification. Coverity documents scans on code commits and pull requests. Infer is documented as running in Meta's CI pipeline.

Do these tools work on code other than C?

Yes. Polyspace covers C, C++ and Ada. Infer covers Java, C, C++, Objective-C and Erlang. Coverity supports 22 languages, and Clang Static Analyzer covers C, C++ and Objective-C.

Sources. Facts on this page come from each vendor's official pages, checked on the dates shown (Asia/Dhaka):

Linthelm is independent and not affiliated with the vendors listed. No vendor paid for inclusion or position. Product names belong to their owners. Features and prices change; confirm details on each official website.