Menu

I ran my Supabase + Stripe security scanner on two popular starters. It was wrong 7 times.
📰

I ran my Supabase + Stripe security scanner on two popular starters. It was wrong 7 times.

DEV Community: nextjs·Sunnatulla·8 days ago
#PIgoaRZK
#devtonextjs#devto#dev#apps#committed
Reading 0:00
15s threshold

I've been building a small static checker for Supabase + Stripe apps, the kind people ship fast with Lovable, Bolt, Cursor or Claude Code. It's a personal project, MIT licensed: vibe-preflight . It runs as a plain Node script or as an Agent Skill, and it looks for six things I keep seeing in rushed apps:

tables in public with Row Level Security never turned on

policies like using (true) that let anyone read or write

the service_role key or a Stripe secret used in browser code

secrets behind NEXT_PUBLIC_ / VITE_ / EXPO_PUBLIC_

Stripe webhook handlers that never call constructEvent

.env files that git tracks

Fixtures and unit tests only tell you so much, so I pointed it at two public MIT starters to see what it does on code I didn't write.

Starter 1: vercel/nextjs-subscription-payments

vibe-preflight 1.0.0 · 56 source files, 3 SQL files · 6 checks

warning schema.sql:66 Policy "Allow public read-only access." on `public.products` (select) lets anyone (signed in or not) read every row.…

Continue reading — create a free account

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