Built in a day.
Exposed in seconds.

See what your app is leaking, before your users do.

$ npx @leakproof/cli
Join early access

THE PROBLEM

The faster AI builds your app, the more holes it leaves behind.

Lovable, Bolt, Replit, Cursor and v0 let anyone launch an app in a day. Open databases, keys in the browser and user data anyone can read often ship with it.

170+Lovable apps leaked their users' data in 2025 alone. Source
CRITICAL · SECURITYTable "profiles" is open to anyonemigrations/001.sql:12
CRITICAL · SECURITYSecret key visible in the browserSignup.tsx:4
SCANNING
HIGH · PRIVACY · GDPRNo privacy policy foundSignup.tsx:12
MEDIUM · PRIVACY · GDPREmails printed to logsSignup.tsx:9

BUILT FOR VIBE-CODED APPS, LIKE ONES MADE WITH

  • Lovable
  • Supabase
  • Bolt
  • Replit
  • Cursor
  • v0
  • Claude Code
  • Codex

WHAT IT CHECKS

Security and privacy,
checked in one scan.

Find what's exposed, see exactly where, and fix it fast.

src/pages/Signup.tsx
1import { supabase } from "../lib/supabase";
2import posthog from "posthog-js";
3import OpenAI from "openai";
4const openai = new OpenAI({ apiKey: "sk-proj-••••••••" });
5
6export default function Signup() {
7 async function handleSubmit({ email, password, phone }) {
8 await supabase.auth.signUp({ email, password });
9 console.log("New signup:", email, phone);
10 posthog.identify(email);
11 }
12 return <SignupForm onSubmit={handleSubmit} />; // no privacy policy link
13}
  1. LINE 4 · CRITICAL · SECURITYA secret key anyone can copyIt ships to every visitor's browser.
  2. LINE 9 · MEDIUM · PRIVACYEmails and phones in your logsReadable by anyone with log access.
  3. LINE 10 · MEDIUM · PRIVACYPersonal data sent to analyticsUsers should know who gets their data.
  4. LINE 12 · HIGH · PRIVACYNo privacy policyCollecting data without telling users why.
Hardcoded secret keysKeys exposed to the browserCommitted .env filesOpen Supabase tablesRules that let everyone inAdmin key in the frontendUnsigned Stripe webhooksAPI routes with no loginNo rate limiting
No privacy policyTrackers before consentData sent to AI and analyticsNo account deletionNo data downloadPersonal data in logs

Privacy checks point to possible gaps, not legal advice.

HOW IT WORKS

Find the leak.
Fix it before it ships.

  1. 1Run the scannpx @leakproof/cli
  2. 2See what's leakingfile, line, how serious
  3. 3Get the fixpaste into Lovable, Cursor, Bolt

The scan finds problems with their file and line, then a re-scan after fixing shows 0 problems left.

TRUST

Your code never leaves
your computer.

$ npx @leakproof/cliRead 42 files on this computerNetwork requests 0Files changed 0$
  • Runs locallyThe scan happens where your code already is.
  • Sends no codeNot your code, not your users' data.
  • Read-onlyIt looks. It never changes a file.
  • Open sourceMIT licensed. Read every check on GitHub.
  • Runs locallyThe scan happens where your code already is.
  • Sends no codeNot your code, not your users' data.
  • Read-onlyIt looks. It never changes a file.
  • Open sourceMIT licensed. Read every check on GitHub.

COMING SOON

Leakproof
Always watching. Always protecting.

It checks every new version of your app and alerts you the moment something is exposed.

EARLY ACCESS

Be one of
our early adopters.

Early access to always-on Leakproof. We only ask for your email.

We use your email only to contact you about early access. Privacy policy

FEEDBACK

Talk to the team.

A question, an idea, or something that broke? Send it here. It goes straight to our inbox, and we reply by email.

Goes to leakproof707@gmail.com. We only use your email to reply.