Code Radar features for local-first review.
Explore source security, dependencies, secrets, code health, reports, hooks, MCP, and GitHub Actions through one evidence model that starts locally.
features
11Code Radar features for local-first review.
Primary coverage11
01Local SAST for Developers and CIDeveloper-first static application security testing that scans source locally, emits SARIF for GitHub code scanning, and gives coding agents deterministic fix context.02Run a local code security scanner where the code already lives.The CLI gives engineers a native SAST and code-health scan loop: run, inspect, fix, and rescan without uploading source to a remote scanner.03Source code vulnerability scanner with actionable findings.Radar focuses on source-code vulnerabilities reviewers need before merge: injection paths, unsafe auth, traversal, secrets, and risky APIs.04Secret scanning CLI for hardcoded keys and API tokens.Use Radar as a local secret scanning CLI to catch hardcoded secrets, API keys, private credentials, and risky placeholders before review.05SCA and dependency vulnerability scanner CLI.Radar checks dependency risk from bundled and cached vulnerability data, giving developers a software composition analysis CLI for supported lockfiles.06Code health scanner for technical debt and review risk.Radar flags duplicate code, oversized files, churn, dead code signals, and AI-generated change risk before technical debt reaches a pull request.07SARIF, JSON, HTML, and terminal reports for code security review.Radar emits compact terminal summaries and structured evidence for GitHub code scanning, CI artifacts, local review, and automation.08Pre-commit security scanner for local Git workflows.Install a local Git hook that runs Radar before risky code reaches a commit, with configurable thresholds for SAST, secrets, dependencies, and code health.09Static code analysis that runs where your code lives.Inspect risky source patterns, insecure APIs, secrets, and structural review debt locally, then carry the same finding evidence into reports, agents, or CI.10Code complexity analysis that runs where your code lives.See how Code complexity analysis fits local review, which evidence Code Radar produces, where coverage ends, and how trusted findings move into CI.11Technical debt scanning that runs where your code lives.See how Technical debt scanning fits local review, which evidence Code Radar produces, where coverage ends, and how trusted findings move into CI.
Use Code Radar features for local-first review. as a decision directory.
Explore source security, dependencies, secrets, code health, reports, hooks, MCP, and GitHub Actions through one evidence model that starts locally. Open the page that matches the concrete decision in front of you, verify its evidence and limits, then continue to the relevant implementation or proof page.
- Scope: Explore source security, dependencies, secrets, code health, reports, hooks, MCP, and GitHub Actions through one evidence model that starts locally.
- Evidence: Inspect the rule identifier, affected file, source-to-sink trace, confidence, remediation path, and exported report before treating a capability as useful.
- Boundary: Static findings support review decisions, but they do not prove runtime exploitability or replace threat modeling, tests, and human approval.
Continue with implementation evidence.
For Code Radar features for local-first review., use these routes to inspect a real artifact, confirm the product boundary, or implement the workflow described in this directory.
Validate the workflow on your own code.
Start with one local scan, inspect the evidence, and expand to reports, agents, or CI only when the signal is useful.