greenlit_check
Grades a deployed web app A to F for what a stranger can exploit—leaked keys, source maps, missing headers—and returns plain-English fixes.
Instructions
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.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"url": "<url>"
},
"name": "greenlit_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The app's address, for example myapp.lovable.app |