I kept seeing Supabase apps accidentally leak data — so I built Supaguard a small scanner
I’ve been working with Supabase for a while and kept noticing the same issue across different projects: apps unintentionally exposing data.
Not hacks — just things like:
Tables left public during testing
RLS policies changed once and never revisited
Old service keys still active
Even teams following “best practices” miss these occasionally.
To solve this for myself, I built Supaguard — a small tool that scans Supabase projects and highlights:
Publicly accessible tables
Potential PII / sensitive data exposure
Hardcoded or risky keys
It’s not meant to replace good security habits, just to catch what humans miss.
I’m sharing it here because this community will probably relate.
I’ve added 2 free scans for anyone who wants to try it.
I’d genuinely love feedback and upvote — what would you want a Supabase security checker to catch that most tools don’t?
Replies