AI codebase analyser and auto vs docs.dev

We added Python AI-app regex prefilters to getdebug and benchmarked against Bandit, Semgrep, and (attempted) vulnhuntr. Here's where each tool actually catches things, and...

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

About AI codebase analyser and auto

We added Python AI-app regex prefilters to getdebug and benchmarked against Bandit, Semgrep, and (attempted) vulnhuntr. Here's where each tool actually catches things, and where they don't. on a Python repo runs in milliseconds, costs zero, and now covers Python AI-app anti-patterns alongside the secrets + dependency-CVE passes it always ran. The interesting part is the benchmark we ran while developing them, against the three other tools anyone would compare us to. vulnhuntr (Protect AI, open source) is the stated category leader for AI-app static analysis.

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.