Most leaked AI keys I've seen this year weren't committed to GitHub. They were compiled into the frontend: a VITE_ or NEXT_PUBLIC_ variable, or a define block like the one Google AI Studio exports use for GEMINI_API_KEY . The key ends up in a JS file every visitor downloads, and scrapers find it.
So I built a checker: keyvaultedge.com/tools/key-leak-check
Enter your site's address. It downloads the page and the scripts it loads from its own site (the same files any visitor gets) and looks for OpenAI, Gemini, Anthropic, Stripe, AWS, GitHub, Slack, SendGrid, Groq, xAI, Hugging Face and Replicate keys.
Results show only the provider and the key's public prefix ( sk-proj-…(164 chars) ), never the key, so it can't be used to harvest other people's keys. Nothing is stored.
Firebase web-config keys ( AIza… next to authDomain ) are flagged "review", not "exposed".…