Static Application Security Testing (SAST) examines source or compiled code without running the application, matching known security-risk patterns before deployment. It scales across large codebases, but it cannot understand every domain-specific correctness failure. section 8.2.2
Flagging an unsanitized parser
A markup parser that places user input directly into generated HTML may trigger a warning for potential XSS. The warning identifies a dangerous pattern, but engineers must determine whether the output is actually exposed to an attack path. section 8.2.2
Use SAST as a fast, broad verification layer:
- Run it on every change alongside linting and type checking. section 8.8.4
- Investigate findings rather than treating every warning as a confirmed vulnerability; pattern-based tools can flag safe code. section 8.2.2
- Pair it with human review, integration tests, and security scanning because domain-specific logic errors remain outside generic rules. section 8.2.2 section 8.8.4
warning: Regular expression has exponential time complexity (no-unsafe-regex)
Inspect a representative SAST-style warning for a regular expression with potentially exponential runtime. section 8.2.2


