Launch security checklist for apps built with Cursor, Lovable or Bolt

Updated November 17, 2026

AI coding tools are very good at making things work. They are not good at noticing what an attacker, a bot or a confused user will do. These are the gaps that show up again and again in apps built with Cursor, Lovable, Bolt, v0 and Replit.

Secrets

  1. No secret keys in client code. Anything with NEXT_PUBLIC_, VITE_ or EXPO_PUBLIC_ ends up in the browser. Service-role keys, Stripe secret keys and OpenAI keys must only be read on the server.
  2. No keys committed to git. Search your history, not just the current files. If a key was ever committed, rotate it.
  3. .env is in .gitignore, and there's a .env.example with names only.

Access

  1. Every API route checks who is calling. A route under /api/ is a public URL even if no button links to it.
  2. Users can only read their own data. Fetching /api/orders?userId=123 and trusting the userId from the request lets anyone read anyone's orders. Take the user from the session instead.
  3. Admin pages check the role on the server, not just by hiding the link.
  4. Database row-level security is on for every table the browser can reach (Supabase, Firebase rules).

Abuse and cost

  1. Rate limits on login, signup, password reset and any route that calls a paid API.
  2. Every retry has a limit and every polling loop has a stop condition. These are what turn one bad night into a four-figure bill.

Failure

  1. No empty catch {} blocks. When something fails, the user should see it and you should hear about it.
  2. Loading and error states on every data fetch, so a slow network doesn't look like a broken app.

Basics people get caught on

  1. A privacy policy and terms page that match what the app actually does, linked from the footer and the signup form.

Automate the list

Twelve items is easy to read once and hard to keep true as your AI keeps editing the code. Periderm checks for these on every scan (keys in client code, admin routes without a role check, user ids trusted from the request, tables without RLS, missing rate limits, runaway loops, silent catch blocks, missing legal pages) along with 150+ other rules, with the file and line for each finding and a fix your AI can apply:

npm i -g periderm-cli
periderm scan

Then add the GitHub Action so every pull request gets the same check, free on public repositories.

more guides