|
Static analysers are loud. Semgrep will happily hand you two hundred findings, most of which aren't reachable, and a reviewer stops reading at forty. It doesn't detect harder — it adjudicates. Every candidate gets checked for real reachability, grounded against CWE/OWASP evidence, argued over by opposing agents, and if it survives all that, patched with a fix that has already been executed in a sandbox to prove it works. Semgrep CE runs as the baseline arm, so the improvement is measured, not asserted. |
|
Design constraints, and why they matter
| Constraint | Consequence |
|---|---|
| Zero cash | No paid APIs, no cloud GPUs, no managed services. Every component is free-tier or open source. |
| Self-hosted | Neo4j, the sandbox and the CI runner all live in local Docker on WSL2. Nothing leaves the machine. |
| One semester | Aug–Nov 2026, vertical slice first — walking skeleton before breadth. |
| Air-gappable | A security tool you can't run on your own infrastructure is a security tool most teams can't adopt. |
The constraints aren't limitations I worked around — they're the reason the thing is adoptable. A PR auditor that ships your source code to a third-party API is a non-starter for exactly the teams that need one most.
Python · Pydantic v2 · Semgrep CE · tree-sitter · Neo4j · Cypher · LangGraph · sentence-transformers · Docker · GitLab CI
| Infra & CI |
|
| Security & Data |
|
| Languages |
|
Most of my day-to-day commits live on GitLab — the numbers below only tell part of the story.
"If it works on my machine, it works on yours."