Code RadarLOCAL SAST GATE
AccountGitHubInstall Radar

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

Run this check locallyInspect sample finding
radar scan . --quick

What Static code analysis means here.

Code Radar uses Static code analysis to turn repository signals into file-level findings, severity, confidence, remediation guidance, and portable review evidence before a pull request is opened.

Capability

Evidence to inspect

Use “Static code analysis that runs where your code 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.
Capability

Run this check locally

Run this check locally

Coverage and concrete signals

Insecure APIs, injection paths, hardcoded secrets, and structural review debt in source files.

  • Audience: Developers who need source-level signal before a pull request exists.
  • Evidence to inspect before you trust the result.: File and line locations, rule identifiers, severity, confidence, and portable SARIF evidence.
  • Boundary: Static checks do not observe runtime configuration, production traffic, or exploitability without human review.
  • Workflow: source patterns · insecure APIs · secrets · SARIF
Feature: sastChoose the next page that matches the remaining implementation or evaluation step.Feature: security scannerChoose the next page that matches the remaining implementation or evaluation step.Feature: reportsChoose the next page that matches the remaining implementation or evaluation step.

From local signal to shared gate.

Static code analysis: Use the smallest workflow that proves value. Each later step should reuse evidence the team already understands. File and line locations, rule identifiers, severity, confidence, and portable SARIF evidence.

StepCommand or actionDecision
1Run a quick local scanIs the signal useful?
2Inspect and repair findingsIs the fix specific and reproducible?
3Export portable evidenceDoes the reviewer need SARIF, JSON, or HTML?
4Promote the trusted threshold to CIWhich severity should block a pull request?
radar scan . --quick
radar scan . --format sarif --fail-on high
Official source

Primary sources

Capability

Start with the problem you need to solve.

Open page →
InstallInstall RadarProofSee sample reportGitHub Actions SARIFGitHub Actions security scanner with SARIF output.

Validate the workflow on your own code.

Apply this page’s evidence to one real repository. For “Static code analysis that runs where your code 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.

Run this check locallyInspect sample finding