What do you check before putting a vibe-coded app in front of real users?

Genuine question for people shipping with Lovable, Bolt, v0 or Cursor. Building fast is the whole point, but the same few problems keep showing up on freshly shipped apps when you look at them from the outside: admin or debug routes left reachable, API endpoints that return another user's data if you change an ID in the URL, Supabase or Firebase tables readable without logging in, and API keys sitting in the frontend JavaScript. None of these need a hacker to find, just someone curious with a browser. So how do you handle it? Do you have a checklist before launch, rely on the platform's defaults, ask the AI to review its own code, or ship and fix later? And which of these has actually bitten you? Disclosure: I work on external recon at Xseth, so this is my day job, but I'd really like to hear what works for people here, with or without tools.

277 views

Add a comment

Replies

Best

the one i keep running into when i read other people's repos is keys in a config file that got committed once. they delete the file later and think it's fixed but it's still sitting in the git history. do you check history from the outside too or only what the app serves?

Always revert the fix to make sure the test actually breaks. An agent produced a clean fix with a new green test, but when the code was backed out, the test still passed. It had written an assertion that completely bypassed the failure path.