ci/sast/php
Code is scanned by a SAST tool
Implements ci/sast for php.
| Severity | info |
| Tiers | 1 |
| Stacks | php |
| Scope | root |
| Kind | outcome |
| Source | library v0.8.0 |
| Selected by | fleetlint-recommended@v0.8.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 vendor/bin/psalm --taint-analysis to the check workflow or the task runner’s check target, or a Semgrep step; list what it reports instead of suppressing it.
Sources
- https://github.com/ossf/scorecard/blob/main/docs/checks.md (standard, SAST)
- https://csrc.nist.gov/pubs/sp/800/218/final (standard, PW.7.2: Perform the code review and/or code analysis based on the organization’s secure coding standards)
- https://fleetlint.org/baseline/#security
- https://psalm.dev/docs/security_analysis/ (spec)
- https://fleetlint.org/stacks/#php
Generated by fleetlint docs from catalog v0.8.0.