Guide · Copy and paste
Vibe coding security prompt: paste this into Lovable, Bolt or v0
AI builders write the code you asked for. Unless you ask, they rarely lock it down. This prompt asks your builder to fix the eight problems that show up most often in AI-built apps. Paste it in before you launch, then check from the outside that the fixes are really there.
The prompt
Why each line is there
Secret keys are the most common problem we see: anything your site sends to the browser is public, and a secret key there lets anyone charge cards, run up your AI bill or read your database. The Supabase anon key and a Stripe pk_ key are meant to be public. Secret ones never are. If one already leaked, rotate it first.
Database rules decide what a stranger can read with your public key. A table without Row Level Security is open to anyone. How to check your RLS.
Storage, server functions and webhooks are where a working app quietly trusts whoever calls it. Source maps and headers are cheap to fix and easy to forget. Leftovers don't leak anything, but they make a launch look broken.
Don't take the builder's word for it
An AI builder will often say "done" when only part of the fix landed, or put a key back while fixing something else. Check from the outside, the way a stranger would. Greenlit reads what your live site actually sends, grades it from A to F, and writes a fix prompt for anything still wrong. Run it after every round of fixes.
From just a link, Greenlit checks secret keys, source maps, headers and launch leftovers. To check your database and storage rules, prove the app is yours first: add the tag the site gives you, or run npx greenlitlab yourapp.com --mine on your own computer. Points 5 and 6 need you or your builder to look; no outside check can see them.
Check your app in 30 seconds
Paste your app's live address. Free, no sign-up, and it reads only what every visitor already sees.
Check your appMore guides