Built for vibe coders · Live

Is your vibe-coded app safe to launch?

Paste a public GitHub repo URL. Get a safe-to-launch score and the first 3 findings, with file and line references where available. No signup.

  • ✓ Leaked secrets, API keys, committed .env
  • ✓ Open databases, public ports, 0.0.0.0/0
  • ✓ Insecure defaults: CORS wildcard, debug mode, disabled auth flags
  • ✓ Dependency issues + PII in log statements

⚡ Free security scan

Paste a public GitHub repo URL. Get your score and the first 3 findings.

No signup. The free scan shows your score and the first 3 findings. Automated scan, not a certification or human review.

…
Scanning…

What the scanner checks

Each maps to a real way vibe-coded apps leak data or get hacked.

🕵️

Leaked secrets

Pattern matches for API keys, tokens, and passwords in source files.

📄

Committed .env

Committed .env and key files.

🗄️

Open databases

Exposed database ports and configs.

⚙️

Insecure defaults

CORS wildcard, debug mode, disabled auth flags.

📦

Dependency vulns

npm audit critical/high findings and unpinned Python requirements.

👁️

Privacy leaks

PII in log statements.

Frequently asked questions

What is a "vibe-coded" app?

An app built primarily with AI coding assistants (Cursor, Copilot, Claude, etc.). They ship fast but often carry leaked secrets, open endpoints, and insecure defaults.

How does Vibe-Scan work?

You paste a GitHub repo URL. The scanner runs pattern checks and shows a score (Safe / Needs work / Do not ship) and the first 3 findings.

Is the free scan really free?

Yes. The free scan shows your score and the first 3 findings. No signup.

Weekly vibe-coding security tips

One email a week: a real finding from a real repo + one fix you can ship in 5 minutes. No spam.