Skip to content

Guides, benchmarks, and case studies

Learn how to find vulnerabilities with taint analysis, investigate real findings, and enforce verified checks in local development and CI/CD.

SAST Is Dead, Long Live SAST!

AI agents have beaten SAST at finding bugs. So what's left for SAST to do? Quite a lot, as it turns out. Finding a bug and proving an entire class of bugs is absent are two very different problems. And when we put a price on the latter, SAST suddenly looked a lot less dead.

Technical note Published Oct 30, 2026

Distilling Frontier Model Security Reviews into a Cheap Deterministic Scan

We're releasing skills that pair an LLM agent with OpenTaint's taint engine. The agent maps your application's attack surface, models the library methods the engine can't see, and writes rules specific to your code — and it can confirm a finding by actually exploiting it. After that, the engine re-scans every future commit on its own, for the cost of CPU.

Guide Published Jun 10, 2026

Taint Analysis for Spring: Security Beyond Syntax

AST-pattern matchers miss what Spring's architecture creates: data flows that cross class boundaries through injected beans, API calls whose danger is decided at bean wiring time, and endpoints linked only through JPA persistence. OpenTaint traces tainted data through every layer, from injected services to database storage to dangerous API calls, distinguishing raw columns from sanitized ones.

Guide Last reviewed Jun 11, 2026

Semgrep vs. CodeQL vs. OpenTaint: XSS Detection Depth Compared

We tested Semgrep, CodeQL, and OpenTaint on five progressively harder XSS cases in a Java Spring application — from direct returns to builder patterns with virtual dispatch — to show where each tool's analysis model hits its limit.

Benchmark Last reviewed Jun 11, 2026