Blog
Security tips for apps built with AI
Practical security tips for apps built with Lovable, Bolt, Cursor and Supabase. No jargon, with prompts you can paste into your coding agent.
· 4 min read
Supabase service_role key leaked? How to rotate it and recover
Leaked your Supabase service_role key? Rotate it, check the logs for abuse, move it server-side and add RLS. Step-by-step recovery for AI-built apps.
Read the post· 5 min read
How to check that Row Level Security is enabled on every Supabase table
Check that Row Level Security is on for every Supabase table: dashboard, SQL queries, a test with the anon key and how to fix gaps. Prompt included.
Read the post· 5 min read
Cursor hooks for security: block risky shell commands and MCP calls
Use Cursor hooks to block risky shell commands, gate MCP tools and keep secrets from the model: a working hooks.json, a deny script and a fail-closed setup.
Read the post· 6 min read
A 10-minute security checklist before you launch a vibe-coded app
Vibe coding security checklist: 10 checks before real users sign up, from leaked secrets and database rules to headers and cookies, each easy to verify.
Read the post· 5 min read
How to check if your API keys are exposed in your JavaScript bundle
Why secret API keys end up in front-end JavaScript built with AI, how to find them with your browser's developer tools, and what to do if one leaked.
Read the post· 5 min read
Supabase anon key vs service_role key: which one can be public?
The Supabase anon (publishable) key is safe to expose; service_role (secret) never is. What each key can do, why Row Level Security matters and how to check.
Read the post· 6 min read
6 security headers every AI-built app should send
Content-Security-Policy, HSTS, frame-ancestors and three more security headers: what each does, a safe starting value and how to check yours.
Read the post
Security guides by platform
Checklists and fix prompts for the tool your app is built with.