What it is:

A lightweight, language-agnostic CLI tool that helps developers validate, sync, convert, and secure .env files. Think of it as a safety net for your environment variables — with commands to scan for secrets, keep .env.example in sync, convert between formats (JSON, YAML, Kubernetes, Docker, GitHub Actions, AWS Secrets Manager, and more), and integrate into CI/CD pipelines.

Built in Rust 🦀, published to 7+ package managers (Cargo, PyPI, npm, Homebrew, Scoop, winget, GitHub Actions), and works across macOS, Linux, and Windows.

Why:

After accidentally leaking AWS credentials via a committed .env file (yes, that story 😅), I realized how fragile our .env workflows really are:

• .env and .env.example drift out of sync

• Sharing secrets with remote teams is risky and tedious

• Every tool expects a different format — manual conversion is error-prone

• No simple, unified way to validate or secure env vars before deploy

I built evnx to solve these pains for myself — and now I'm sharing it so others can benefit (and help make it better).

Link:

• Complete Story : https://www.evnx.dev/blog/why-i-built-evnx

• Code Repo: https://github.com/urwithajit9/evnx

• Docs/Guide Web: https://www.evnx.dev

Would love to hear your thoughts!

• What's your biggest .env pain point?

• Have you tried similar tools? What worked or didn't?

• Any features you'd love to see added?

Drop a comment below 👇 or open an issue on GitHub. All feedback welcome — this is very much a community-driven project. If you like, give star and fork to contribute.