Static Code Analysis Tools logopeterindia.net
Knowledge Hub

Static Code Analysis Tools

A curated directory of static code analysis tools — code quality management, vulnerability detection and architecture analysis for Java, .NET, Python, JavaScript, C/C++ and many other languages, from platforms to open-source linters.

49 topics•5 categories•Updated October 2026

Multi-Language Quality & Security Platforms

11 entries

Platforms that analyse many languages in the IDE, pull request and CI pipeline.

Architecture & Code Intelligence

5 entries

Tools that map structure, dependencies, metrics and technical debt.

Language-Specific & Safety-Critical Analyzers

7 entries

Analyzers for particular languages, IDEs or regulated industries.

Open-Source Analyzers & Linters

19 entries

Free tools, grouped here by the language they target.

Related Pages

7 entries

Related directories on this site.

Frequently Asked Questions

What is static code analysis?

Static code analysis examines source code without running it to find bugs, security weaknesses, style violations and maintainability problems early in development.

How does it differ from SAST?

SAST is the security-focused subset of static analysis. General static analysis also covers code quality, style, complexity and technical debt, and many tools do both.

Linter, static analyzer or code quality platform?

Linters enforce style and catch simple errors in one language, static analyzers do deeper data-flow analysis, and platforms such as SonarQube track quality across many languages and over time.

Which products changed names or owners?

SonarCloud is now SonarQube Cloud, Codiga has joined Datadog, and the Squore and Sonatype scanner pages have moved to new addresses.

Are the links checked?

Links were checked when this page was updated. Squore, Codiga, CodeMRI and Cppcheck needed a browser check and all loaded. Polyspace and GitClear blocked automated checks and are not listed.