← All free resources

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.

6 checksAbout 15 minutesNo code needed for most

0 of 6 checked

  1. 01

    Who can see whose data

    What goes wrong

    Your 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
    1. In Supabase, open the Table Editor. Each table shows whether RLS is on.
    2. 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 fix

    Turn RLS on for every table, and write rules that only return rows belonging to the logged-in user.

  2. 02

    API keys and secrets

    What goes wrong

    A 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
    1. Open your live site, open the browser's developer tools, and search all of the site's files for sk- and sk_ (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.
    2. In your code, search for service_role and anything named SECRET used outside a server function.
    The fix

    Move 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.

  3. 03

    Who can do what

    What goes wrong

    Admin 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
    1. Log in as a normal user and type your admin page's address straight into the browser, for example yourapp.com/admin.
    2. If the page loads, or its buttons work, it isn't locked.
    The fix

    Check the user's role on the server, or in your database rules, for every admin action. Hiding the button isn't enough.

  4. 04

    Usage limits and your bill

    What goes wrong

    An 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
    1. For each AI feature, ask what stops someone from pressing the button 10,000 times.
    2. Look in your AI provider's billing settings for a monthly budget or alert.
    The fix

    Add a per-user limit on expensive features, require a login for them, and set budget alerts with every provider that bills you by usage.

  5. 05

    Payments

    What goes wrong

    The 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
    1. Find your Stripe webhook code. It should call constructEvent with your webhook signing secret.
    2. Check that prices come from Stripe price IDs or your server, never from the page.
    The fix

    Verify every webhook signature, and set prices on the server so the browser can't change them.

  6. 06

    Logins and accounts

    What goes wrong

    Sign-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
    1. Sign up with an email inbox you can see. Can you get in before clicking the confirmation link?
    2. In Supabase, check that email confirmation is turned on under Authentication settings.
    The fix

    Turn 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.