Developer workflow
What is local analysis?
Running the analysis itself on a developer's machine, from the command line or a git hook, without waiting for CI.
A CLI closes the feedback loop from minutes to seconds and makes the tool scriptable, useful for pre-commit hooks, custom pipelines and debugging why CI disagrees with your machine.
It also matters for confidentiality: a CLI that analyzes fully locally never sends source code anywhere, which is sometimes the only way a tool passes review in a regulated environment.
Not the same as CLI: A CLI is any command-line client, including one that only starts a scan in the vendor's cloud. Local analysis means the scan itself runs on your machine.
What to look for
- Whether analysis is genuinely local or a thin client for a cloud API
- Parity between CLI results and server results
- Pre-commit framework integration
- Whether the CLI is available on the free tier
Best 20 code quality, security and code review tools that run analysis locally
Every tool in the directory whose documentation covers this, 17 fully and 3 partially. Full support is shown first. Shown in a random order that changes on every visit, so no tool gets an advantage from its position.
Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.
Code Security Platform
Local Scanner CLI runs code, secrets, dependency and IaC scans locally; a pre-commit hook checks staged code for secrets.
AI Coding Agent
codex-security install-hook adds a pre-commit scan blocking high-severity findings.
Code Security Platform
Checkmarx One CLI ('cx') plus VS Code extension pre-commit scans; SCA Resolver runs resolution on-prem.
AI Coding Agent
/code-review and /security-review run in the terminal; /claude-security local scan needs a paid plan.
Code Quality Platform
Codacy Analysis CLI runs static analysis fully locally, no API round-trip; pre-commit hook not confirmed.
PR Review Tool
CLI for local and CI review, with git hooks support for pre-commit scanning
PR Review Tool
cr CLI reviews committed, staged, unstaged and untracked local changes; 3 reviews/hour on Free
Code Quality Platform
CLI runs local analysis, goal supervision and batch analysis with script-friendly output
Code Security Platform
corgea setup-hooks; offline deps commands need no network
PR Review Tool
/review-bugbot reviews branch or uncommitted changes pre-push; patch-ID dedup skips the later PR review.
Code Security Platform
CodeQL CLI creates and analyzes databases locally or in any CI; push protection blocks at push time
PR Review Tool
greptile review runs full-fidelity local branch review in ~60s; exit codes usable in hooks
Code Quality Platform
Open-source CLI runs qlty check and qlty fmt locally, wired as pre-commit and pre-push git hooks
Code Security Platform
`semgrep scan`/`semgrep ci` CLI plus a pre-commit framework hook; org-wide hook settings need Platform.
Code Security Platform
Snyk CLI runs local pre-commit and CI/CD scans across code, deps, container, IaC, secrets.
Code Quality Platform
SonarQube CLI analyzes local changes and staged files and runs 'sonar analyze secrets'.
Code Security Platform
Veracode CLI and Pipeline Scan JAR/Docker run locally; --allow-dirty re-verifies uncommitted changes
Code Quality Platform
CLI queries results and uploads coverage; analysis runs on DeepSource infrastructure, no local pre-commit scan documented.
AI Coding Agent
Gemini CLI runs agentic tasks in the terminal; no pre-commit hook or local review command documented.
PR Review Tool
Pre-PR review of uncommitted changes runs in the IDE plugin; no standalone CLI documented
Related terms
FAQ
What is local analysis?
Running the analysis itself on a developer's machine, from the command line or a git hook, without waiting for CI.
How many tools in the directory run analysis locally?
All 20 tools in this directory run analysis locally, 17 fully and 3 partially:
Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.
What should you check when comparing tools that run analysis locally?
Four things:
- Whether analysis is genuinely local or a thin client for a cloud API
- Parity between CLI results and server results
- Pre-commit framework integration
- Whether the CLI is available on the free tier