Developer builds four security tools in a month, documenting every limitation openly

A developer built four interconnected security tools over one month, each designed to expose its own limitations rather than hide them. The first tool, secfix, attempts to verify scanner findings by executing flagged code in a sandboxed environment, but testing against a real Django app revealed it could confirm zero of 84 findings without manual input. The second tool, husk, extracted the sandbox into a standalone component and included adversarial tests to verify isolation claims, while openly acknowledging it shares the host kernel and is not a hypervisor replacement. A third tool, witness, added audit-hook-based introspection to capture what untrusted code actually attempted before the sandbox blocked it. The project's central argument is that a security tool's documentation is only as reliable as the tests backing its weakest claim.