ci/sast/any
Code is scanned by a SAST tool
The stack-neutral implementation of ci/sast: it checks stacks without an implementation of their own and repositories where no stack is detected, and its satisfiers count for every stack.
| Severity | info |
| Tiers | 1 |
| Stacks | any |
| Scope | root |
| Kind | outcome |
| Source | library v0.2.0 |
| Selected by | fleetlint-recommended@v0.2.0 |
Requirement
CodeQL (github/codeql-action), Semgrep or Opengrep, the GitLab SAST template or component, or SonarQube runs in CI or the task runner.
Why
SAST follows data from input to dangerous sinks across files, which per-file linters do not; on GitHub CodeQL is free for public repositories.
Fix
Add a CodeQL workflow (GitHub advanced setup), include the GitLab SAST component, or add a Semgrep step to CI; with CodeQL default setup, declare it with accept:.
Agent instruction: Add a CodeQL workflow (github/codeql-action init/analyze, pinned) for the repository’s languages, or on GitLab include components/sast; run it on pull requests and weekly.
See: https://fleetlint.org/baseline/#security
Generated by fleetlint docs from catalog v0.2.0.