Free · self-check · no code
The 15-point pre-drive inspection
A free security self-check for apps built with Lovable, Bolt, Cursor or Replit. Most founders get through it in about 30 minutes, and you don't need to be a developer.
- Is RLS turned on for every table?In Supabase, open the Table Editor and check that each table shows "RLS enabled". If one doesn't, anyone with your public key can read it.
- Does every RLS table have real read and write policies?A policy like
using (true)lets everyone in. Each policy should name exactly who can read and write. - Can user A open user B's records?Create two accounts. Copy the URL or ID of a record that belongs to user B, then open it while logged in as user A.
- Are there secrets in the browser?Open DevTools, go to Sources, and search for
service_role,sk_liveandsecret. None of these should appear. - Are your admin pages protected?Try opening your admin or dashboard routes while logged out, and again as a regular user.
- Does your Stripe webhook verify signatures?Your server should call
constructEventwith the webhook secret. If it doesn't, anyone can fake a "payment succeeded" event. - Are paid features checked on the server?Hiding a button only changes what users see. The server has to refuse the request too.
- Can the price be changed from the browser?Edit the amount or quantity in the checkout request and send it again. The server should ignore the change.
- Do password-reset links expire?Check that a reset link works only once and stops working after a short time.
- Are email-sending endpoints rate-limited?Send the same signup or invite request 20 times in a row. If all 20 go through, someone else can use your app to send spam.
- Do error messages leak internals?Error messages shouldn't show stack traces, table names or SQL to the user.
- Are uploaded files private?Check whether files users upload end up in a public storage bucket.
- Is CORS open to every site?An API that requires login shouldn't return
Access-Control-Allow-Origin: *. - Was a
.envfile ever committed?Check your repo, and also its git history. - Did you re-check after the AI's last change?Run checks 3, 5 and 7 again after each AI edit. That's where things break most often.
Your ticks are saved only in this browser. Nothing is sent anywhere.
Prefer the dummies do it?
A Dummy Run covers the external checks within 24 hours. A Full Crash Test covers all 15 points plus manual testing, and comes with repair prompts you can paste into your AI builder.
This checklist covers the most common issues. Passing it doesn't mean your app is secure.