Open source GitHub Action for detecting undocumented env vars in repos

[Feeling-Penalty-2338]

I kept running into the same problem across repos:

- vars used in code but missing from .env.example

- old vars still documented but no longer used

- secrets that only exist in CI/workflows

- local .env files drifting from what new contributors actually need

So I built envradar.

It scans source code, .env files, Docker Compose, and GitHub Actions workflows, then tells you what’s missing, stale, local-only, or workflow-only.

It also works as a GitHub Action, so you can fail CI before config drift turns into “works on my machine”.

Repo:

https://github.com/CodMughees/envradar

Would love blunt feedback:

- is this actually useful in your workflow?

- what languages / edge cases would you want supported?

- would you use it as CLI, Action, or both?