Run 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.

Run this check locally Inspect sample finding

radar scan . --quick

Interactive cockpit

Running `radar` opens a keyboard-driven cockpit with Dashboard, Settings, Integrations, License, and Results screens.

Fast and full profiles
Readable finding detail
Config generation
License status

Local CLI

Evidence to inspect

Use “Run a local code security scanner where the code already lives.” as the scope for this decision: verify the input, finding detail, workflow handoff, and product boundary before you install or buy.

CriterionEvidence to inspectBoundary

Input scopeSelected files, configuration, scan mode, and enabled rules.Only included paths and configured checks are evaluated.

Finding detailFile, line, rule ID, severity, explanation, and repair direction.Illustrative output is not a result from your repository.

Workflow handoffLocal result, report format, agent context, and optional CI signal.Enable exports or CI only when the workflow needs them.

Decision fitUse the same criteria on a real repository before choosing a plan or tool.No universal winner or guaranteed outcome is claimed.

Local CLI

Run this check locally

Scriptable output

Automation stays predictable. Use the same scan engine for terminal summaries, SARIF, JSON, and HTML.

radar scan . --format json > radar-report.json
radar scan . --format sarif --fail-on high

Official source

Primary sources

NISTSecure Software Development Framework (SSDF) 1.1
GitHub DocsUploading a SARIF file to GitHub

Validate the workflow on your own code.

Apply this page’s evidence to one real repository. For “Run a local code security scanner where the code already lives.”, confirm which finding is produced, whether the proposed next step is reproducible, and where local scanning, reports, agents, or CI should stop or expand.