Analysis Tools
A curated, community-maintained list of static analysis and linting tools across many languages.analysis-tools-dev/static-analysis
- Stars
- 14.9k
- Forks
- 1.5k
- Licence
- MIT
- Language
- Rust
- Last update
- 4 days ago
- Type
- Curated list
What it is
This is an organized directory of static analysis tools, which are programs that check source code for bugs, style problems, and quality issues without running it. It groups tools by programming language, build tool, config file type, and other areas, and marks proprietary tools and ones no longer maintained. The website analysis-tools.dev is built from this repository and adds rankings and comments.
- Find a linter for a language such as Python, Go, or Rust by browsing its section
- Check which tools are open source versus proprietary using the symbols legend
- Look up tools for config files, Dockerfiles, Terraform, or CI pipelines
- Review the contribution criteria before proposing a new tool
Great for
- Developers looking for a linter or analyzer for a specific language
- Teams comparing static analysis options before choosing one
- Students learning what code quality tools exist
- Maintainers who want to suggest a tool for the list, if it meets the stated criteria
Not ideal for
- Anyone wanting to run a tool directly: this is a list, not an installable program
- Users who need a verdict on which tool is best, since the README only lists tools and does not rank them
- Projects that need tools with active maintenance, as the list includes deprecated entries marked with a warning symbol
How to get it
- 1
Read it online
Clone the repository to browse it locally
git clone https://github.com/analysis-tools-dev/static-analysis - 2
Run it
- Open the repository on GitHub or the website at analysis-tools.dev
- Pick a programming language or category from the table of contents
- Read the one-line description and check the symbols for proprietary or deprecated status
- Follow the link to the tool's own documentation to install it
- 3
Get the most out of it
- Use the website analysis-tools.dev for rankings and user comments not included in the README
- Check the symbols legend before choosing a tool, especially the warning and community-not-recommended icons
- Read the contribution criteria in CONTRIBUTING.md if you want to submit a tool
Downloads
Strengths
- Broad coverage across many programming languages and file types
- Clearly marks proprietary tools and those not recommended or not recently updated
- Contribution criteria are published, which helps keep entries vetted
Trade-offs
- As a list, it does not describe how each tool performs or compare features in depth
- The README is truncated here, so the full set of entries could not be checked
- Entries link out to external sites that may change over time
How it compares
| Project | Stars | Type | Level | Updated | Best for |
|---|---|---|---|---|---|
| static-analysis (this) | 14.9k | Curated list | beginner | 4 days ago | Developers looking for a linter or analyzer for a specific language |
| awesome-security | 15.1k | Curated list | beginner | 10 months ago | Security learners looking for well-known tools in a given area |
| ruff | 50.4k | CLI | beginner | 4 days ago | Python developers who want one tool for linting and formatting |
| SwiftLint | 19.8k | Dev tool | beginner | 20 days ago | iOS and macOS developers who want consistent Swift style across a team |
| infer | 15.7k | Dev tool | intermediate | 4 days ago | Developers working on Java, C, C++, or Objective-C codebases |
| rubocop | 12.9k | Dev tool | beginner | 4 days ago | Ruby developers who want consistent style across a project |
Stats synced from GitHub. The assessment above was drafted with AI from the project's README on 2026-10-29 and may miss recent changes — check the README before relying on a command. MIT licence: free to use, modify and distribute, including commercially, as long as you keep the copyright notice.