Security scanning
What is taint analysis?
Tracing untrusted input from where it enters the program (source) to where it could do damage (sink).
Taint analysis is the main difference between a data-flow SAST engine and a pattern matcher. It follows a value across assignments, function calls and files, asking whether attacker-controlled data can reach a dangerous operation without being sanitized along the way.
The payoff is precision: a hardcoded string passed to a SQL query is not a vulnerability, and taint analysis knows the difference. It costs build time and needs per-framework modeling to know which functions count as sources and sinks, which is why fast pattern-based rules still have a place for simple checks and team conventions.
What to look for
- Whether analysis crosses file and function boundaries, or stops at one function
- Framework coverage for your stack, since modeling is per-framework work
- Whether the tool shows the full source-to-sink path in the finding
- Scan-time impact on large repositories
Best 10 code quality, security and code review tools with taint analysis
Every tool in the directory whose documentation covers this, 8 fully and 2 partially. Full support is shown first. Shown in a random order that changes on every visit, so no tool gets an advantage from its position.
Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.
Code Security Platform
Data flow analysis inside AI Deep Review; credit-metered, Pro plan and above
Code Security Platform
Attack Vector shows source-to-sink tainted data flow; Best Fix Location is chosen within that data-flow graph.
PR Review Tool
AI Deep Scan traces untrusted input to sensitive sinks with call stacks; separately billed
Code Security Platform
Cross-file source-to-sink taint tab in BLAST Full View
Code Security Platform
CodeQL taint tracking; model packs add taint-flow models and threat models add taint sources, both public preview
Code Security Platform
Taint tracking with constant/symbolic propagation; cross-file interfile taint requires Pro Engine and full scans only.
Code Security Platform
Source-to-sink data flow analysis with AI-learned sources, sinks and sanitizers; data-flow visualization.
Code Quality Platform
Tracks data flow from untrusted sources to dangerous sinks; Advanced SAST sold separately.
AI Coding Agent
Cloud finding pages show call-path and data-flow context 'when available'; no taint engine.
AI Coding Agent
Managed Claude Security "traces data flows across files" per vendor docs; beta, Enterprise plan only.
Related terms
FAQ
What is taint analysis?
Tracing untrusted input from where it enters the program (source) to where it could do damage (sink).
How many tools in the directory offer taint analysis?
10 of the 20 tools in this directory offer taint analysis, 8 fully and 2 partially:
Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.
What should you check when comparing tools with taint analysis?
Four things:
- Whether analysis crosses file and function boundaries, or stops at one function
- Framework coverage for your stack, since modeling is per-framework work
- Whether the tool shows the full source-to-sink path in the finding
- Scan-time impact on large repositories