SAST vs code scanning in GitHub workflows

Understand the difference between scanner engines, SARIF output, GitHub code scanning alerts, and pull-request gates.

Apply this guide locally Inspect product evidence

radar scan . --quick

Engine and destination

A SAST tool finds issues. GitHub code scanning is where SARIF alerts can be displayed and tracked. Radar emits SARIF so local findings can travel into that workflow.

Guide

Evidence to inspect

Use “SAST vs code scanning in GitHub workflows” 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.

Guide

Apply this guide locally

Review before the alert

Run the local scan before a pull request exists, then upload SARIF in GitHub Actions when the branch needs shared evidence.

Official source

Primary sources

NISTSecure Software Development Framework (SSDF) 1.1
OASIS OpenSARIF 2.1.0 standard

Validate the workflow on your own code.

Apply this page’s evidence to one real repository. For “SAST vs code scanning in GitHub workflows”, confirm which finding is produced, whether the proposed next step is reproducible, and where local scanning, reports, agents, or CI should stop or expand.