greenlitlab
Checks Firebase Realtime Database and Firestore rules for public access, using owner-only checks to test whether strangers can read or list data and reporting findings with remediation prompts.
Checks Supabase-backed apps for exposed service_role keys, publicly readable tables, publicly listable storage buckets, and open sign-ups without email confirmation; also translates Supabase Security Advisor results and project-file scans into plain-language findings and fix prompts.
Greenlit
Is your AI-built app safe to launch? Greenlit grades a deployed app from A to F for what a stranger can use against it. It explains each problem in plain words and gives you a prompt to paste back into Lovable, Bolt, v0, Replit or Emergent that fixes it. Run it again after the fix, and it shows what got fixed.
In the browser: greenlit.priberry.com. Paste your app's address. Nothing to install.
On your computer:
npx greenlitlab myapp.lovable.appWhat it checks
Check | Where it runs |
Secret keys in the JavaScript every visitor downloads: 32 kinds, including Stripe, OpenAI, Anthropic, OpenRouter, Gemini, AWS, GitHub, Supabase secret keys, Telegram bots, private keys and service-account JSON | everywhere |
A Supabase | everywhere |
Source maps that hand out your source code | everywhere |
Clickjacking (no | everywhere |
Supabase tables anyone can read with the public key | your own app: |
Supabase storage buckets that list their files to anyone | your own app: |
Supabase sign-up open to anyone without email confirmation | your own app: |
A public | your own app: |
Firebase Realtime Database and Firestore open to everyone | your own app: |
Greenlit reads all of the app's own scripts, including lazy-loaded pages and the app's own CDN, and tells you if a check ran out of room or couldn't read the code. Grades follow the danger: one critical problem is an F whatever else is right, one high problem means C at best, and small things such as missing headers take 20 points at most. What your host controls and you can't change is shown but costs nothing.
On the website, choose "Check my database here" after a check: you add a tag made from a key only your browser holds, so nobody else can use your tag. On the website it checks standard Supabase and Firebase addresses only.
Supabase no longer lists a project's tables for the public key, so the database check tests the tables your app's code names, tells you how many it tested, and says so plainly when it could test none.
The owner-only checks ask for a row count (Supabase), one file or document name (storage, Firebase), or the sign-up settings, never for data, and never write anything. They run only when you say the app is yours, because testing someone else's database without permission isn't OK.
Related MCP server: unchore-defend
Launch readiness, beyond leaks
Check | Where it runs |
A page that loads from a developer-only address, plain-http content, Stripe in test mode, a default title, "noindex", AI calls from the browser, a test email sender, unlocked sign-in cookies | everywhere |
Plain http that doesn't redirect to https; an app that lets any website read a signed-in visitor's data | everywhere |
No DMARC record or a broken SPF record on your own domain | everywhere, custom domains only |
Personal columns (email, phone, password…) in tables strangers can read; backend functions listed for review | your own app: |
Rules that are too loose, tables strangers can change: Supabase's Security Advisor in plain words |
|
Always-true policies, tables without Row Level Security, unverified payment webhooks, secrets behind a public prefix |
|
Backups, spending limits, a separate test database, outage alerts |
|
Only what Greenlit confirmed moves the grade. What it couldn't see is said out loud, and what only you know is asked. Greenlit never signs in, never reads your users' data and never writes to your database.
Commands
npx greenlitlab <url> # grade an app
npx greenlitlab <url> --mine # your own app: database checks too
npx greenlitlab <url> --prompt 1 # print fix prompt 1 only (pipe it to pbcopy)
npx greenlitlab <url> --prompt all # every fix in one prompt, worst first
npx greenlitlab <url> --json # the full result
npx greenlitlab <url> --fail-on high # exit 1 if anything this serious is found, for CI
npx greenlitlab questions # seven things only you know, with a fix for each gap
npx greenlitlab scan [folder] # read your project's files before you deploy
npx greenlitlab advisor results.json # Supabase's Security Advisor, in plain wordsThe last result for each app is kept in ~/.greenlit/sites/ (grade, finding ids and titles only, never keys) so the next run can show what changed.
In Claude, Cursor, VS Code and other agents
Add Greenlit as an MCP server:
{ "mcpServers": { "greenlit": { "command": "npx", "args": ["-y", "greenlitlab@0.2.0", "mcp"] } } }Then ask your agent to check the app it just deployed and apply the fixes. The greenlit_check tool returns the grade, every finding and its fix prompt.
Made by Priberry
Greenlit comes from Priberry, the crash-test lab for AI agents. Its sister tools: Crumple crash-tests coding agents, and Tare shows what they cost.
Apache-2.0. Found a problem? Open an issue, or see SECURITY.md.
Available Tools
4 toolsgreenlit_advisorARead-only
Turn Supabase's Security or Performance Advisor results into plain-English findings with a fix prompt for each, worst first. Get the results from the Supabase MCP server's get_advisors tool (type "security") for the user's project, then pass them here as lints. This is the reliable way to learn which rules are too loose and whether strangers can change or delete data, which no outside check can see.
Inputs: lints (required).
greenlit_checkARead-only
Grade a deployed web app (built with Lovable, Bolt, v0, Replit, Emergent or by hand) A to F for what a stranger can use against it: secret keys shipped in its JavaScript (Stripe, OpenAI, OpenRouter, Supabase secret keys and 28 more kinds), a Supabase service_role key in the browser, source maps, clickjacking and missing security headers, plus launch basics (developer-only addresses, Stripe test mode, a test email sender, no https redirect, open CORS, missing DMARC on a custom domain). Every finding has a plain-English reason and a fix prompt; allFixes has every fix in one prompt, worst first. Reads only what the site serves to every visitor. Call it again after a fix: change shows what got fixed. For the user's own app, have them run npx greenlitlab <url> --mine: it also checks which database tables and storage buckets anyone can read, open sign-up, and public .env or .git files.
Inputs: url (required).
greenlit_questionsARead-only
Seven launch questions only the app's owner can answer (backups and restore, separate test database, hard spending limits, payment webhook checks, outage alerts, email sender, database plan). Call with no arguments to get the questions and options to ask the user. Call with answers ({questionId: optionKey}) to get, for each gap, the fact that makes it matter and a fix prompt. Answers are the owner's word, never graded.
Inputs: answers.
greenlit_scanARead-only
Read a project folder on this computer for launch mistakes that can't be seen from outside, before deploying: Row Level Security policies whose condition is just true, tables created without RLS, Supabase edge functions with verify_jwt = false, Stripe webhook handlers that never verify the signature, secrets behind a public prefix (VITE_, NEXT_PUBLIC_), a tracked .env file, and an agent config with a writable database connection. Pattern-based, not a full code review. Reads names in .env files, never values. Each finding has a fix prompt.
Inputs: dir.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Scan a deployed app URL for exposed keys, open Supabase tables and missing security headers.
Check a deployed web app for security headers, SEO, accessibility and performance, with a grade.
Free, read-only ship-readiness check for Replit, Lovable and Bolt apps.
Security checks for AI-built apps (Lovable, Supabase, Bolt): RLS, headers, monitoring, fixes.
Related MCP Servers
- AlicenseAqualityDmaintenanceAudit any website for privacy, security, accessibility, and performance issues — with scores, grades, and actionable fix instructions. No account required.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables grading a website's security headers with per-gap fixes and a README badge, and analyzing logs, code, configs or suspicious messages to determine what happened, how severe it is, and what to fix first. Requests are masked for sensitive data and automatically retried across multiple AI providers when one refuses, subject to a defensive-use-only policy.1MIT
- AlicenseAqualityBmaintenanceScan a deployed site for an exposed Supabase service_role key and audit Row Level Security from your AI coding agent.2460 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents and developers to audit any URL or domain for seven critical OWASP HTTP security headers, returning an A+ to F grade plus actionable Nginx, Apache, Caddy, and Cloudflare remediation snippets. It also probes /.well-known/security.txt and /security.txt to surface responsible vulnerability disclosure contacts, bug bounty scopes, and PGP keys.2MIT