ci: add Radar security scanning (secrets + SCA)#257
Merged
Conversation
Adds a Security Scan workflow that runs Radar CLI (EurekaDevSecOps/radarctl) — Opengrep (SAST), Gitleaks (secrets), and Grype (SCA) — on pull requests and pushes to main, complementing the existing CodeQL coverage. Runs fully local (no telemetry token, nothing leaves the runner) on ubuntu-latest, since Radar's scanners run as Docker containers. The gate uses '-t high', so only high/critical findings fail the job; moderate/low print for triage. A repo-root .gitleaks.toml keeps the full default secret ruleset for shipped code (src/, bin/, scripts/) while allowlisting the tests/ tree, whose fixtures intentionally contain fake, credential-shaped values.
The initial run surfaced 8 high-severity Opengrep SAST findings, all of them command-injection rules firing on inherent CLI behavior — 'capy run' spawning the user's own command, deploy adapters shelling out to aws/wrangler, clipboard helpers, and build/test tooling. These are by-design for a local CLI, not real vulnerabilities, and Opengrep also overlaps the existing CodeQL SAST workflow. Drop opengrep so Radar covers what CodeQL does not — secret scanning (Gitleaks) and dependency/SCA (Grype) — and let CodeQL own SAST.
cvince
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Security Scan workflow running Radar CLI — Gitleaks (secrets) and Grype (SCA) — on PRs and pushes to
main. SAST is intentionally left to the existing CodeQL workflow (see below).Behavior
EUREKA_AGENT_TOKEN, so no findings leave the runner.ubuntu-latest(not the self-hosted CI runner) because Radar's scanners run as Docker containers.main" policy via-t high: only high/critical findings fail the job; moderate/low still print to the log for triage.Why secrets + SCA only (no Opengrep SAST)
capy runrunning the user's own command, deploy adapters shelling toaws/wrangler, clipboard helpers, build/test tooling) rather than real vulnerabilities.Secret-scan allowlist
.gitleaks.tomlkeeps the full default ruleset for shipped code (src/,bin/,scripts/) while allowlisting thetests/tree, whose fixtures intentionally hardcode fake, credential-shaped values.gitleaks dirinvocation Radar runs: 12 fixture findings to 0 with the allowlist.Rollout: not yet a required status check — flip it in branch protection once the initial findings are triaged.