Working
Taint engine with provenance, source-to-sink paths
Open source, agent-native
Lint-Owl is a static analyzer whose result is the data-flow path from an untrusted source to a dangerous sink. It proves that user input actually reaches the exploit, and shows the exact chain.
This box runs a small taint tracer in your browser, built from the same sources, sanitizers, and sinks as the real analyzer. Edit the code and press Scan to see the path it finds.
runs entirely in your browser, same sources, sanitizers, and sinks as the CLI
Most tools point at a line and say this looks risky. Lint-Owl follows the taint from where it enters to where it detonates.
Flag local smells. No data flow across statements, no source-to-sink reasoning.
Matches syntactic patterns. A pattern does not prove the input actually reaches the sink through assignments.
A real dataflow engine, but heavy. Build a database, learn a query language. Overkill for one file.
One small binary whose output is the tainted path itself, and an MCP tool an AI asks "does user input reach this exec".
Each is a source-and-sink set, so more classes are just data.
Taint engine with provenance, source-to-sink paths
CLI, HTTP API + console, MCP server
Python-subset front end, 5 vuln classes
Sanitizer awareness and control flow
Results are candidate paths a human confirms. No sanitizer or control-flow awareness yet, and that honesty is written into the README.