.env file committed to the repo
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 25 points from that category, once per scan, no matter how many places it turns up.
What it detects
A .env file (which typically holds secrets) was found tracked in the project directory.
Why it matters
A committed .env hands every credential in it to anyone with repo access, including future collaborators, CI logs, and anyone who clones a fork. Even after you delete the file, the values stay in git history. Treat every value in it as exposed.
How to fix it
Run git rm --cached .env to untrack the file while keeping it locally, add .env to .gitignore, and commit. Create a .env.example with the same keys and placeholder values so setup stays documented. Rotate every secret the file contained. If the repo is public or widely cloned, scrub history with git filter-repo.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo