Build a GitHub Actions security scanner gate
Turn scanner output into PR annotations, SARIF alerts, GitHub code scanning evidence, and deterministic merge thresholds.
radar scan . --quickA useful gate is explicit
Choose the severity threshold, publish the report, and keep the action comment concise enough for reviewers to act on.
Guide
Evidence to inspect
Use “Build a GitHub Actions security scanner gate” 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.
Official source
Primary sources
Validate the workflow on your own code.
Apply this page’s evidence to one real repository. For “Build a GitHub Actions security scanner gate”, confirm which finding is produced, whether the proposed next step is reproducible, and where local scanning, reports, agents, or CI should stop or expand.