What it checks
- Stack and client library fingerprint with a curated free CVE pack (including CVE-2025-29927), Firebase path probes, OpenAPI GET expansion, Appwrite/PocketBase/Hasura/Convex, Fix now playbooks, Serious vs Hardening tips, and a README score badge
- Auth surface map, open-redirect probes, GraphQL introspection checks, and nested Supabase selects (read only)
- Risk score 0-100, peer comparison by stack (anonymous buckets only), TLS expiry and HTTPS redirect notes
- Export Markdown report, copy a shareable summary, and one-click copy a README badge snippet; scan again anytime to see what improved
Ownership
Optional: prove you control the host with a file at /.well-known/vibelocked-verify.txt or a DNS TXT record on _vibelocked-verify. Until then we only run anonymous reads. After proof we add deeper read-only checks (still no mutating RPCs or throwaway signups).
The data behind it
We ran these same read-only checks against 2,511 live vibe-coded apps on nine platforms. About one in five Supabase apps left a database table open to anyone. Read the study.
Limits
This is an outside read of a public URL. A clean result is not a guarantee. Cap: about 20 same-origin scripts, about 1.5 MB each, short timeouts, capped probe counts.
Related: exposed .env, .git, and source maps, anon vs service role, CORS misconfiguration, CSP for vibe-coded apps.