SAST
Named by 18 kept items in this workspace.
17 items name it under tools and 1 under classification.technologies.
The items that name it 18
Static Application Security Testing
Static Application Security Testing
static application security testing; recommended for scanning AI-generated code
Scans AI-generated code for security flaws before it merges
Scanning selected repositories to identify likely vulnerabilities
Scans source code for known bad patterns; catches many but not all AI-generated code flaws
Rule-based tool that catches known insecure code anti-patterns; described as missing architectural design flaws and phantom/transitive dependencies
Scans source code for known bad patterns
Static analysis security testing; noted as unable to find IDOR-type vulnerabilities like the one in this case
Pattern-based matching of code against known vulnerability patterns; deterministic, cheap, runs on every commit/PR and in the IDE for early feedback; gates CI/CD.
catches plain SQL injection where input runs into a query with no parameterized statement; noted it would not have caught the WordPress cross-request bug
Deterministic tooling for baseline hygiene and rule enforcement, used alongside LLM triage
Static application security testing, part of existing AppSec controls that remain essential but insufficient alone against agentic risk
Static Application Security Testing
Static analysis that detects issues like SQL injection (e.g. string concatenation into a SQL query) but without native visibility into reachability, attacker control, or data sensitivity
Traces data flow from deep link sources (URI parameters, Intent extras) to sinks such as WebView URL loading, startActivity(), file access and SQL queries; flags contains and startsWith host checks
Source-code analysis that cannot look inside compiled third-party SDKs (.aar, .jar, .framework, .xcframework) unless it analyzes the compiled artifact
In every workspace you can read 19
Security
All technologies in this workspace.