True Churn is the headline. This page is the rest of the box — the Code Browser, the AI Agent Scan, the AI Code Scan, the GitHub Action and the desktop app — shown as the screens they actually are. Fifteen screens, one per feature — click any picture to enlarge it.
↓ fifteen screens belowEvery scan writes one self-contained page that reads the code: five tabs that never leave the screen — Changes (the side-by-side diff, for comparisons), Overview, Files, Classes and Visualiser — with the browser’s Back button and a breadcrumb on every screen. A single-project scan gets the same page without the Changes tab.
Read it in the guide: The Code Browser · the papers behind the counters: Papers.
Named SDK calls, model endpoints, exec-on-model-output, raw API keys, non-Western providers — found by reading the code, never by running it. Every flag names the file and line; the Agent Map draws the AI bill of materials as a picture.
Also in the box, without a picture: the AI bill of materials (native and CycloneDX) and the policy gate (--gate) that blocks unapproved providers in CI; the baseline that fails a merge only on new findings. CLI / CI reference.
Files scored for generated-code characteristics — HIGH, Elevated, Normal — as a review aid. It tells you where to look first; it never claims to know who wrote a line. The paper says exactly what it can and cannot do.
Two lines in a workflow file. On every pull request, inside your own runner: the churn summary and agent findings as a PR comment, SARIF into the Security tab, and an optional merge gate. The engine downloads itself; a licence is built in for the beta.
Set it up in five minutes · See it on a real PR · an MCP server lets your own agents call the engine (CLI / CI).
macOS, Windows and Linux. Pick a mode, point it at two snapshots or one project, and read churn, the AI code scan, the agent scan and the Code Browser in one local window — nothing phones home.