.env file with real values present in codebase
A .env file containing non-placeholder values was found in the scanned code. If this is committed to git, every secret in it is exposed to anyone with repo access — forever, via git history.
What the check contributes
Rule SEC003runs as part of CodeCordon's deterministic static-analysis pass. When it matches, the finding includes the source file, line number, severity, explanation, and a redacted snippet so the developer can inspect the evidence directly.
Recommended remediation
Add .env* to .gitignore, remove the file from git history (git filter-repo or BFG), and rotate every credential it contains. Keep a .env.example with placeholder values instead.
How to use this result
- 1. Open the reported line. Confirm the match is active application code rather than a fixture, example, or false positive.
- 2. Apply the remediation in context. Preserve the intended behavior while removing the dangerous pattern.
- 3. Scan again. Verify the known pattern no longer appears, then continue with tests and any runtime or human security review appropriate to the application.
Limits of this check
A match is a review signal, not proof of exploitability. No match means only that this specific known pattern was not found in the applicable files. It does not rule out equivalent code, business-logic flaws, runtime vulnerabilities, or novel attack paths.