SecurityDevToolsAISaaS

LeakProbe — Secret Leak Check for Vibe-Coded Sites

One-shot secret and config leak scan for vibe-coded websites

Problem
More people ship websites generated with AI, but almost nobody checks their build output for hardcoded API keys, Supabase anon keys, or exposed env vars. A developer already built a secret checker specifically for vibe-coded sites, confirming the pain is real and concentrated around the last step before launch.
Solution
Enter a domain or upload build artifacts, and scan JS bundles, source maps, and public config files for sensitive strings. Rank findings by severity and provide a one-line diff to fix each issue. Integrate into a GitHub Action or deploy hook to run automatically on every ship.
Users
Indie developers shipping with AI coding tools, vibe coders, and small studios
MVP
Enter a URL or GitHub repo; scan JS bundles, source maps, and env leaks; match known prefixes for OpenAI, Stripe, Supabase, etc.; generate a GitHub Action; free first scan with paid fix report
Revenue
Free scan for lead gen; paid fix reports and continuous monitoring subscription ($5-15/mo); GitHub Marketplace per-repo billing
Why now
AI-generated code volume is exploding and with it the attack surface. These scanners run purely client-side or at the edge, making them cheap and ideal for an indie security tool.

Source discussions · 3

  1. Hacker NewsShow HN: I built a vibe coded website checker for leaked secrets4↑ 4
  2. Hacker NewsShow HN: Deterministic security scanner for Model Context Protocol2↑ 0
  3. Hacker NewsShow HN: Rowan, an open-source SAST scanner for AI apps (code, models, MCP)"1↑ 0
← Back to list