corral records every scan — what it audited, what it rejected, and why — natively in DuckDB. This page runs DuckDB itself, compiled to WebAssembly, in your browser, against a real dataset: six scans of Flask, a library we didn't write. Real SQL, no backend. Query the rejections as readily as the results — the point of a ledger is that it also records the parts that don't flatter you. The same schema federates to MotherDuck(a DSN flip) as a shared warehouse across a distributed dev shop.
Tables: scans (6 whole-repo scans) ·scan_files (1,446 per-file rows — every candidate the scan considered, audited or rejected, with the reason). Two real DuckDB tables, shipped as parquet and queried client-side. Recorded 2026-08-02against Flask — a library we did not write — on the workspace substrate.corral fleet federates the same schema to MotherDuck for streaming-live. See the audits these rows came from →