I read a lot of apps generated with Lovable, Bolt, v0 and Replit - usually after something broke. The same five problems show up in most of them, and none of them need a security background to check. This is the list I run before an app gets a public link.
1. Supabase keys
The anon/publishable key in the frontend is fine; the service_role (or sb_secret_...) key is not. Copy the key VALUE from Supabase -> Settings -> API and search both your repo and the built bundle for that value - the key is a token, it does not contain the word "service_role". If it is anywhere the browser can load, rotate it in the dashboard (rotating the legacy key regenerates the JWT secret and logs every user out).
2. Row Level Security
Supabase dashboard -> Authentication -> Policies (or Database -> Policies). A table with RLS off is readable by every visitor. A SELECT policy USING (true) that applies to anon (no TO clause, or TO anon/public) is also readable by every visitor; USING (true) TO authenticated means every logged-in user, which is sometimes what you want. Check INSERT/UPDATE/DELETE the same way: WITH CHECK (true) means anyone can write.
3. Checks that live only in the UI
A hidden button is not access control. In the browser's Network tab, copy a request as cURL, delete the Authorization header (keep apikey) and replay it - that is the logged-out view. Then replay it with the header but change the record id to someone else's - that is the other-user view, where most of these apps leak.
4. Unhandled input
Send an empty form, a 10,000-character string, and a negative number to every form. Anything that shows an error with code in it, goes blank, or saves a record it should have rejected is a bug a stranger will find first.
5. Dependencies
Run npm audit once (it needs package-lock.json; if the project only has bun.lockb, run bun audit or create the lock first). For Python: pip install pip-audit, then pip-audit. Generators pick versions from their training data, which can be behind.
If any of these turns up something you can't read, post the error text in the comments (not the keys) and I'll tell you what it means.
Top comments (0)