Building LaunchCheck — a free pre-launch checker for AI-built apps (Lovable, Bolt, Cursor). Finds leaked keys, open Supabase tables, broken mobile layouts.
@Missum_AI Thanks, I'd missed that. Without an ownership check, a write test is an attack tool. LaunchCheck never tries to write to your tables, so no ownership check yet. If I add one: a file. Apps on a default Lovable or Vercel subdomain can't add DNS records.
Just shipped a small tool: paste your Lovable/Bolt/Replit app's URL and it tests it in a real browser (desktop + phone).
It flags leaked API keys, Supabase tables anyone can read, login redirects to localhost and broken mobile layouts.
Free, no signup.
@steffdoesthings Free check: no, you rerun it. Pro rechecks after each deploy (via a deploy hook) and daily, so a fix shows up on the next run. I just fixed a bug in the daily run, so I'll confirm it after the next one at 21:00 UTC. Emails only go out for new problems, not fixes.
Supabase has two keys and mixing them up is a classic vibe-coding hole:
anon / publishable → fine in the browser, RLS protects you service_role / secret → bypasses RLS. If it's in your frontend, anyone can read and delete everything.
Search your built JS for "service_role".
@Missum_AI The table check is read-only: it only reads (max 3 rows per table) and never writes. Anyone can paste any public URL, and there’s no ownership check. Would you use an opt-in write test if it existed?
@Missum_AI No real-world data yet, so I can’t say which one fires most.
It actually queries with the anon key. It pulls the key from the site’s JS, then tries a read-only select on each table. If rows come back, it’s flagged. It never writes, so insert/update policies aren’t tested.