Menu

5 things to check before you share your vibe-coded app with real users
📰

5 things to check before you share your vibe-coded app with real users

DEV Community: security·Fuad Poladov·about 2 hours ago
#ucAduaZb
#devtosecurity#devto#dev#every#audit
Reading 0:00
15s threshold

I read a lot of apps generated with Lovable, Bolt, v0 and Replit - usually after something broke. The same five problems show up in most of them, and none of them need a security background to check. This is the list I run before an app gets a public link.

1. Supabase keys

The anon/publishable key in the frontend is fine; the service_role (or sb_secret_... ) key is not. Copy the key VALUE from Supabase -> Settings -> API and search both your repo and the built bundle for that value - the key is a token, it does not contain the word "service_role". If it is anywhere the browser can load, rotate it in the dashboard (rotating the legacy key regenerates the JWT secret and logs every user out).

2. Row Level Security

Supabase dashboard -> Authentication -> Policies (or Database -> Policies). A table with RLS off is readable by every visitor.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.