Why this exists
Vendor documentation is difficult to compare.
New static analysis, security scanning and AI-assisted review tools are released regularly. Existing ones change which capabilities are free, which require an enterprise plan, which languages they cover and which deployment models they support.
Each vendor describes its own product in its own terms, and limitations are rarely stated directly. Comparing two tools therefore means reading both sets of documentation in full and working out what has been left out.
Review Radar answers a narrower question: does a specific tool support a specific capability, and on which plan.
What we track
The same criteria for every tool.
Each tool is recorded against the same set of capabilities, so tools built for different purposes can still be compared where they overlap:
Each entry also records supported languages, integrations, deployment model (cloud, self-hosted, air-gapped) and the plan tier each capability requires. Whether a tool supports a capability, and whether it supports it on a given plan, are recorded as separate facts.
How entries stay current
Checked against the vendor's own documentation.
Each entry is reviewed against public sources: product documentation, pricing pages, changelogs and release notes. A capability is recorded as supported only where it is documented. Where the documentation doesn't mention it, it is recorded as not available, with a note saying so. The few cases where the evidence is unclear are marked unknown.
Entries are re-checked on a rolling basis. Every tool page shows the date its entry was last verified.
This doesn't replace the official documentation.
Every entry here is a summary of what a vendor published on a particular date. Plans get restructured, capabilities move between tiers, and prices change without anyone announcing it.
Who it's for
Engineers and security teams evaluating tools.
Engineers, security teams and platform leads shortlisting a tool during procurement, a migration or a compliance review. It assumes you already know roughly which capabilities you need and want to check which tools provide them.
Who publishes it
Published by Codacy.
Review Radar is published by Codacy. Codacy builds code quality, AI code review and code security tools, so tracking what every tool in this market supports is part of its day-to-day work.
Codacy is also one of the 20 tools listed. The directory is built so that doesn't tilt it:
- Codacy is recorded against the same criteria, from the same kind of public sources, as every other tool.
- Tool lists are shown in a random order on every visit, so no tool gets an advantage from its position.
- Corrections are welcome for any tool, Codacy included.
The directory is researched and maintained by Cláudia Fernandes.
Corrections
Submit a correction.
Spotted something wrong or out of date? Tell us what should change and, if you can, where the vendor documents it. Every correction is checked against the vendor's own documentation before a listing changes.
Thanks, your correction was sent. We'll check it against the vendor's documentation.