Free checklist Vibe-coded app security checklist
Six checks you can run on your own app, most of them from the browser. They cover the problems that turn up most often in apps built with Lovable, Bolt, Cursor, Claude, Codex, Replit or v0.
0 of 6 checked
- 01
Who can see whose data
What goes wrongYour app talks to its database straight from the browser using a public key. If row level security is off, or a rule says anyone can read, every user's records can be read by anyone who opens the browser's developer tools.
Check it yourself- In Supabase, open the Table Editor. Each table shows whether RLS is on.
- Sign up two accounts. Logged in as one, open a page that belongs to the other, for example by changing the ID in the address bar.
The fixTurn RLS on for every table, and write rules that only return rows belonging to the logged-in user.
- 02
API keys and secrets
What goes wrongA secret key for OpenAI, Stripe or your database ends up in the code that runs in the browser. Anyone can copy it and use it on your account.
Check it yourself- Open your live site, open the browser's developer tools, and search all of the site's files for
sk-andsk_(in Chrome: Sources tab, then Cmd+Option+F on a Mac or Ctrl+Shift+F on Windows). That's how OpenAI and Stripe secret keys start. View source only shows the HTML, not the JavaScript where keys end up. - In your code, search for
service_roleand anything named SECRET used outside a server function.
The fixMove anything that needs a secret into a server or edge function. Then rotate every key that was exposed: make a new one and delete the old one.
- Open your live site, open the browser's developer tools, and search all of the site's files for
- 03
Who can do what
What goes wrongAdmin pages and buttons are hidden from normal users, but the server behind them never checks who's asking. Anyone who finds the address can use them.
Check it yourself- Log in as a normal user and type your admin page's address straight into the browser, for example
yourapp.com/admin. - If the page loads, or its buttons work, it isn't locked.
The fixCheck the user's role on the server, or in your database rules, for every admin action. Hiding the button isn't enough.
- Log in as a normal user and type your admin page's address straight into the browser, for example
- 04
Usage limits and your bill
What goes wrongAn AI feature, sign-up form or email sender has no limit. One script can call it thousands of times and run up your OpenAI, Supabase or email bill overnight.
Check it yourself- For each AI feature, ask what stops someone from pressing the button 10,000 times.
- Look in your AI provider's billing settings for a monthly budget or alert.
The fixAdd a per-user limit on expensive features, require a login for them, and set budget alerts with every provider that bills you by usage.
- 05
Payments
What goes wrongThe app trusts the browser about what was paid, or the Stripe webhook doesn't check Stripe's signature. Someone can fake a "payment succeeded" message or change the price before checkout.
Check it yourself- Find your Stripe webhook code. It should call
constructEventwith your webhook signing secret. - Check that prices come from Stripe price IDs or your server, never from the page.
The fixVerify every webhook signature, and set prices on the server so the browser can't change them.
- Find your Stripe webhook code. It should call
- 06
Logins and accounts
What goes wrongSign-up doesn't confirm the email address, so someone can make an account in another person's name. Custom login code skips the protections your auth provider already has.
Check it yourself- Sign up with an email inbox you can see. Can you get in before clicking the confirmation link?
- In Supabase, check that email confirmation is turned on under Authentication settings.
The fixTurn on email confirmation and use your auth provider's built-in sign-up and password reset instead of custom code.
Found something, or not sure what you're looking at
Send us your app and we'll run these checks and more on your code, then walk you through what to fix on one 30-minute call. It's free.