greenlıt

For apps built with Lovable · Bolt · v0 · Replit · Emergent

Know it's safe
before you launch.

Greenlit looks at your app the way a stranger would. It finds leaked keys and open data, tells you in plain words what each one means, and writes the prompt that fixes it.

Free. No sign-up. Reads only what every visitor already sees.

Example result
F

Your users' data or your accounts are exposed right now.

your-app.lovable.app · built with Lovable

  • Stripe secret key in your JavaScriptcritical
  • Anyone can read the profiles tablecritical
  • No Content-Security-Policylow
Fix 1 · paste into LovableCopy

My app ships a Stripe secret key in its frontend code. Move every call that uses it into a Supabase Edge Function, read the key from a secret there, and remove it from the client…

A after three prompts and one key change

~ — zsh

Run npx greenlitlab in your terminal and this is what you'll see.

Check. Fix. Check again.

  1. 01Check

    Paste your app's address. Usually in under thirty seconds, you get a grade from A to F and every problem a stranger could use.

  2. 02Fix

    Each problem comes with a prompt written for your builder. Paste them in one at a time, worst first.

  3. 03Check again

    Run it once the fix is live. The grade goes up, and you know the fix worked instead of hoping it did.

What it looks for

Only what Greenlit confirmed moves your grade. What it couldn't see, it says. What only you know, it asks.

Secret keys in your code
32 kinds, from Stripe, OpenAI, OpenRouter and AWS to Telegram bots and private keys, that anyone can copy from the JavaScript your site sends.
on the web
Your database's master key
A Supabase service_role or sb_secret_ key in the browser lets anyone read and change everything.
on the web
Your source code, handed out
Source maps that let anyone download the code behind your app.
on the web
Clickjacking and missing headers
The settings that stop other sites from framing your app or injecting scripts into it.
on the web
Leftovers that break a live app
A page still pointing at a developer's computer, payments in test mode, a test email sender, a default title, or a setting that hides you from Google.
on the web
Email people will trust
On your own domain: the records that stop others sending email as you, and keep your sign-up emails out of spam.
on the web
Data anyone can read
Supabase tables, storage buckets and Firebase data open to the whole internet. Counted, never read.
your computer
Sign-up that lets anyone in
Accounts without email confirmation turn "signed-in users only" rules into "anyone".
your computer
Rules that let everyone in
Policies that check nothing, functions that skip sign-in, payment messages nobody verifies. Read from your project's files, or from Supabase's own advisor in plain words.
your computer
What only you know
Backups, spending limits, a separate test database. Seven questions, asked after every check. Never graded, because we can't verify your answers.
on the web
Files that should never be online
A public .env file with all your keys, or the .git folder with your whole code history.
your computer

Run it where you build

Your own app, deeper

Greenlit can check your database too, once it knows the app is yours: add one tag and check it here, or run it on your computer.

$ npx greenlitlab myapp.lovable.app --mine
Inside your agent

Add it as an MCP server in Claude, Cursor or VS Code, and ask your agent to check what it just deployed.

$ npx -y greenlitlab mcp
In CI

Fail the build when something serious opens up after a change.

$ npx greenlitlab $APP_URL --fail-on high

We never sign in to your app, never read your users' data and never write to your database. The database checks run only for the person who controls the app: on your own computer, or here once you add a tag to it that only your browser can use. Like any visitor, they use only the public key your app already ships. A check's result is kept for a few minutes and each site is rate-limited, to make it hard to use us to hammer a site. A public report exists only if you turn it on with a tag on your own app, and it comes down when you remove the tag. No cookies and no ad trackers; visits are counted cookie-free by Cloudflare Web Analytics. Open source, so you can check us too.