blog
Security for apps you built by prompting.
What leaks out of Lovable, Replit, Bolt, v0, Cursor and appgnt apps, how to check yours in a few minutes, and the exact prompts that fix it. Written for founders, not security teams.
Don't become a LinkedIn post
A founder ships an AI-built app Saturday. By Wednesday a stranger has the OpenAI key. By Thursday LinkedIn has 9,000 takes. The 10 minutes that prevent it.
The vibe coding security checklist
Vibe coding security checklist: 12 checks before strangers use your app. Leaked keys, Supabase RLS, Firebase rules, .env in GitHub, each with a fix prompt.
Is Lovable secure? And is your Lovable app?
Is Lovable secure? Yes. Apps built with it leak in four ways: VITE_ keys, the service_role key, tables without RLS, GitHub sync. How to check yours and fix it.
Supabase RLS in Lovable apps: check every table
Supabase RLS in Lovable apps: find every table with RLS disabled, spot policies that let everyone in, and fix them with copy-paste SQL or a Lovable prompt.
API key exposed in your frontend JavaScript: the 10-minute response
API key exposed in frontend JavaScript? The 10-minute response: rotate it, check usage, move the call server-side, clean VITE_ vars, verify it is gone.
Replit app security: six holes to check
Replit app security: Replit is trusted, with Secrets, Auth and its own scanner. Agent-built apps still ship six holes: VITE_ keys, routes without auth, open CORS.
Reading about it is step one.
Step two takes a minute: paste your app's address and see what it is actually showing strangers.