I built a free VS Code extension that catches leaked secrets before you commit them
The problem Last year I nearly committed a Stripe live key to a public repo. Caught it manually at the last second. But it made me think — why doesn't VS Code warn me about this automatically? So I...

Source: DEV Community
The problem Last year I nearly committed a Stripe live key to a public repo. Caught it manually at the last second. But it made me think — why doesn't VS Code warn me about this automatically? So I built EnvGuard. What it does EnvGuard is a free VS Code extension that adds 6 things your .env files have always needed: 🔐 Secret Scanner — detects 30+ patterns (AWS keys, GitHub tokens, Stripe keys, JWT tokens) with red underlines before you commit ✅ Schema Validation — define a .env.schema file, get instant errors for missing/wrong keys 🔄 Environment Switcher — save dev/staging/prod profiles, switch with one click 🔍 Diff Viewer — compare any two .env files side by side 📋 Example Generator — auto-generate .env.example from your real .env 🖥️ Dashboard — visual overview of all keys, security score, profiles How the secret scanner works Add this to your .env: JWT_SECRET=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9... EnvGuard immediately shows a red wavy underline and adds to Problems panel: "Pot