Scan your code for vulnerabilities with an open-source code security scanner
A feature can work and still trust the wrong caller or accept work without a limit. Review the code behind those decisions before launch.
npm install --save-dev @sitecmd/cli
npx sitecmd audit .
The CLI runs on your computer or in your CI, and your code stays there.
What it finds on a demo project
SiteCMD CLI 2.0.0
Demo project: Supabase app with row level security gaps
npx sitecmd audit .
SiteCMD Code Scan - .
Checked: November 9, 2026
Framework: Express
Issues: 6 total | critical 0 | high 2 | medium 4 | low 0
High (2)
- [Database Analysis · security] Client-facing Supabase code references a service-role credential name - src/components/AdminPanel.jsx:3
- [Database Analysis · security] Client-facing Supabase write policy has an unconditional row condition - supabase/migrations/20260101000000_init.sql:13
Medium (4)
- [Database Analysis · data] Client-facing Supabase operation has no matching local RLS policy - src/components/Dashboard.jsx:8
- [Database Analysis · data] Client-facing Supabase table has RLS enabled but no local policies - src/components/Dashboard.jsx:7
- [Database Analysis · security] No recognized local RLS enablement for a client-accessed Supabase table - src/components/Dashboard.jsx:6
- [Database Analysis · security] Client-facing Supabase write policy has no clear per-row caller boundary - supabase/migrations/20260101000000_init.sql:16
Your code passes? Now watch your site.
How to read code security scan findings
The SiteCMD CLI audits your project's code where you run it. Treat each finding as something to investigate; another part of the app may already handle it.
Frequently asked questions
Can a code security scanner prove my app is secure?
No. A finding points to a pattern to investigate, and a clean audit isn't a security guarantee. Follow the actual request path and test the permissions and failure cases that matter to the feature.
Where should I start with a vibe coding security checklist?
Start with who can access each record, how your app confirms payment events, which endpoints have limits and where your keys live. SiteCMD's pre-launch checklist and AI code audit guides cover the rest of a release review.
Read the launch checklist and AI code audit
Website security
Catch leaked API keys and exposed files before someone uses them against you.
Pre-launch website checklist: 12 production checks
Twelve pre-launch checks for builds, critical flows, SEO, accessibility, security, performance, monitoring, rollback, and post-deploy proof.
AI-generated code audit: 7 mistakes before shipping
Audit AI-generated code for exposed secrets, swallowed errors, authorization gaps, unsafe SQL, reckless retries, and stale React effects.