vibe-shield — Open-source 92-rule static security scanner & MCP server for Next.js + Supabase apps #53266
Replies: 1 comment
|
Good list of diff-time bugs — the service_role client reaching a One boundary worth designing for, since your rules are static: RLS failures are state, not code. Three cases a static scanner cannot see, that a verification step should cover:
The strongest handoff for a scanner in this space is a read-only verification query set per finding: the exact catalog query, the role it runs as, and the expected pass/fail result — so an agent, or a human, can prove the fix landed on the deployed project and not just in the diff. If vibe-shield emits that set alongside each rule, it closes the gap between "the code says safe" and "the database is safe" without needing any runtime access. |
Uh oh!
There was an error while loading. Please reload this page.
Hey everyone 👋
While building Next.js App Router + Supabase projects with AI coding agents (Claude Code, Cursor, OpenCode), I kept noticing the same silent security bugs slipping into diffs:
service_roleclients accidentally imported into modules reachable from"use client"componentsPOST/PUT/DELETEroute handlersuser_idis trusted directly fromreq.json()instead ofsupabase.auth.getUser()USING (true)/WITH CHECK (true)pitfallsI built an open-source, zero-config static scanner, Agent Skill (
SKILL.md), and MCP server called vibe-shield:👉 GitHub Repo: https://github.com/avivgerz-hue/vibe-shield
You can run a 1-second local scan in any project:
npx -y @vibefoundry/vibe-shield@latest scan .All reactions