CodMughees

CodMughees / envradar

Public

Catch undocumented, unused, and drifting environment variables in your repo

cli developer-tools devops productivity python
69
0
100% credibility
Found Apr 08, 2026 at 213 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Python
AI Summary

envradar scans code repositories to detect environment variables that are used but undocumented, documented but unused, or only present locally or in workflows.

How It Works

1
🔍 Discover the setup checker

While fixing confusing setups for new team members on your project, you find a friendly tool that spots missing or forgotten project settings.

2
📥 Add it to your project

You easily include the checker in your project's automatic review steps so it runs whenever changes happen.

3
🚀 Run the first check

It scans your entire project in seconds and highlights exactly where settings are missing, unused, or hidden.

4
📋 Review the clear report

You get a simple list with counts and spots in your files, making it easy to see what needs fixing.

5
✏️ Update your guides

You add missing settings to your example guide and clean up old ones based on the helpful pointers.

6
📄 Generate fresh examples

The tool creates an up-to-date example setup file and team guide, ready to share.

🎉 Team onboards smoothly

New contributors now set up your project quickly without 'works on my machine' headaches, keeping everyone happy.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 213 to 69 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is envradar?

EnvRadar is a Python CLI and GitHub Action that scans repos to catch undocumented, unused, and drifting environment variables in code, .env files, Docker Compose setups, and workflows. It spots vars used in runtime (like Python os.environ or JS process.env) but absent from .env.example, stale documented ones, local-only secrets, and CI-exclusive references such as ${{ secrets.NAME }}. Run `envradar . --strict` in CI or generate .env.example files to prevent onboarding headaches and "works on my machine" bugs.

Why is it gaining traction?

Broad support for Python, JavaScript, Go, Rust, Java, PHP, .NET, and even C++ getenv patterns sets it apart from narrow linters, while GitHub annotations, job summaries, and outputs like missing-count make CI integration dead simple. Strict mode blocks merges on drift, and config ignores noisy vars like GITHUB_TOKEN alongside placeholders for safe examples. Devs hook it into pull requests for try-catch-like safety on GitHub Actions environments.

Who should use this?

Repo maintainers tired of env mismatches breaking previews, teams with frequent contributor handoffs, or polyglot projects mixing Python backends with JS frontends and Docker. Ideal for GitHub-heavy workflows where undocumented local vars or workflow-only secrets slow deploys.

Verdict

Solid docs and zero-fluff setup make this 69-star, 1.0% credibility Python tool a low-risk add to CI pipelines despite its youth – install via pipx and gate merges today to catch drift early.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.