2026-11-17 · Daily security tips
Is your live app still running npm run dev?
Some apps on a VPS, Replit or Docker box went live with npm run dev and never changed. The dev server is made for your own machine. It serves your original, unminified source files to anyone who asks, and Vite's dev server has had several file-read bugs that only matter once it is reachable from the internet.
Check: view source on your live site. If you see /@vite/client, or yoursite.com/src/main.tsx (or main.jsx) opens your code, you are on the dev server. On Next.js, make sure the start command is next start, not next dev.
Fix: run npm run build and serve the built output (dist/) with your host or a static server. vite preview isn't meant for production either. If the dev server was public for a while, update Vite and rotate the keys in your .env.
Is your live site exposing something like this?
The free quick check looks at what your site already serves publicly: secret keys in your JavaScript, open /.env files and /.git folders, Supabase tables readable with your public key, and missing security headers. No sign-up needed.
No app handy?
No sign-up. Read-only public-resource and protocol metadata checks. No model prompts or tool execution. Scan only sites you own or are allowed to test.
Run on every deploy or use from Cursor / Claude Code via MCP →