fleetlint Policy for a fleet of repositories
v0.10
Getting started

ci/sast/php

Code is scanned by a SAST tool

Implements ci/sast for php.

Severityinfo
Tiers1
Stacksphp
Scoperoot
Kindoutcome
Sourcelibrary v0.7.0
Selected byfleetlint-recommended@v0.7.0

Requirement

Psalm’s taint analysis (psalm --taint-analysis) runs in CI or the task runner; or a stack-neutral scanner (CodeQL, Semgrep, GitLab SAST, SonarQube).

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

Run vendor/bin/psalm --taint-analysis in the check workflow, or add a Semgrep step.

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.

Sources


Generated by fleetlint docs from catalog v0.7.0.