"Vibe coding" means describing what you want and letting an AI write the code. It's fast, and it works. What it skips is the part where someone reads the code and asks what a stranger could do with it. This checklist is that part, in plain words. It doesn't replace a professional review for apps that handle health, money or other sensitive data, but it catches the mistakes that cause most real trouble.
Before anything else: run your builder's own check
Most builders now have one. Lovable runs a security scan when you open the publish dialog, and Bolt has a security audit in its publish menu. Use them first; they see your project from the inside. The checks below are about the live app, from the outside.
Keys and secrets
1. No secret keys in the browser
Open your published app, then the browser's developer tools → Sources, and search the JavaScript for sk_live, sk-, sk-ant-, service_role, sb_secret_ and private_key. Anything you find, every visitor can copy. Move those calls to a server function and rotate the key.
2. No secrets behind a "public" prefix
Variables named VITE_… or NEXT_PUBLIC_… are written into the code visitors download (Vite docs, Next.js docs). Only public values belong there.
3. No files that shouldn't be online
Try /.env, /.git/config and a few .map files on your live address. They should all fail. If one loads, deploy only your build output, not the whole project folder.
Your database
4. Row Level Security on every Supabase table
With RLS on and good policies, the public key is harmless. With it off, anyone can read the table. See is the Supabase anon key safe?.
5. Firebase rules that match the owner
No if true rules, and rules that compare the user's id with the data's owner. See is a Firebase API key a secret?.
6. Users can't see or change each other's data
Make two test accounts. As user A, try to open user B's records, change their profile, or set your own role to admin or plan to paid. All of it should fail.
Sign-up and sign-in
7. Email confirmation is on
Otherwise anyone can sign up with an address they don't own.
8. Logins only send people back to your site
Social logins redirect back to your app after sign-in. Make sure only your own addresses are on the allow list, and that your Site URL isn't still localhost.
9. Sign-in and sign-up have limits
Repeated wrong passwords or mass sign-ups should be slowed down or blocked. Many back ends have this built in; check it's on.
The connection and the browser
10. HTTPS everywhere, with security headers
Every page on HTTPS, plain HTTP redirecting to it, and headers like HSTS and a Content-Security-Policy. Our security headers guide lists the ones that matter, and the headers checker tests them in seconds.
11. CORS isn't open to every website
"Allow all origins" fixes CORS errors and also lets any website call your API from a visitor's browser. Allow only your own domains.
The rest of launch
12. Legal pages that match what the app does
If you collect emails or take payments, you need a privacy policy and terms, and payment providers expect clear refund and contact details. Make sure they describe your app, not a template, and check which laws apply where you and your users are.
After launch
Every new prompt can change your app. Re-check after bigger changes, and keep an eye on your providers' usage pages for anything unusual.
Check most of this in one go
Securick's free scan runs 46 of these tests from your public URL in about a minute, including:
- #1 Stripe live secret key exposed Free
- #5 Supabase service key exposed Free
- #10 Secret values in public env variables Free
- #11 .env file public Free
- #12 .git folder public Free
- #13 JavaScript source maps public Free
- #19 HTTP redirects to HTTPS Free
- #22 HSTS header Free
- #23 Content-Security-Policy present Free
- #29 Not open to every website Free
Pro runs all 130, including sign-up settings and legal pages; Deep (on domains you verify) checks database access and whether users can reach each other's data.
Questions
Is vibe-coded software less secure than hand-written code?
Not by nature, but it's often shipped without anyone reading it, so common mistakes like keys in the front end or open database tables slip through. A checklist and a scan catch most of them.
How long does this checklist take?
About an hour by hand the first time. A scan covers most outside checks in a minute or two; the database and two-user checks take longest.
Do I need a penetration test?
For apps that handle health, financial or other sensitive data, a professional review is worth it. For most early apps, fixing what this checklist finds removes the most common risks first.