fleetlint Policy for a fleet of repositories
v0.11 (latest)
Getting started

ci/sast

Code is scanned by a SAST tool

A capability: each stack checks it with its own tools, and every implementation that runs must pass. Implemented for any, php, ruby.

Severityinfo
Tiers1
Stacksany
Scoperoot
Kindcapability
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

Requirement

A static application security test runs in CI or the task runner: a stack-neutral scanner (CodeQL, Semgrep or Opengrep, GitLab SAST, SonarQube) or the stack’s own taint analysis (Brakeman for Rails, Psalm’s taint analysis for PHP). Linters with security rules count under the lint rules, not here. CodeQL default setup, which leaves no file in the repository, and other scanners are declared with accept:.

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, a Semgrep step for a language CodeQL does not analyze, or on GitLab include components/sast; run it on pull requests and weekly.

Sources


Generated by fleetlint docs from catalog v0.8.0.