As developers, we often rely on .env files to manage sensitive environment variables. But have you ever thought about how insecure this practice is? .env files store secrets in plain text, making them vulnerable to accidental leaks, unauthorized access, or exposure in public repositories.
Thatโs why I built CryptEnv โ a simple yet powerful tool that lets you securely store, manage, and use environment variables without exposing them in plaintext.
๐ Why You Need CryptEnv
โ No More Plaintext Secrets โ Store your environment variables in an encrypted, global base store instead of a raw .env file.
โ On-Demand Decryption โ Your secrets are only decrypted when needed, and you must unlock them using a password before accessing them.
โ Auto-Clearing Environment โ Once your process finishes, CryptEnv automatically clears the variables, leaving no trace behind.
โ Easy Integration โ Works seamlessly with any programming language or framework that uses environment variables.
โ Open Source โ Completely free and available for the community! Check it out on GitHub: CryptEnv Repository
๐ง How CryptEnv Works
1๏ธโฃ Store your secrets securely
crypt-env set DATABASE_URL "postgres://user:password@host/db"
2๏ธโฃ Unlock and use them in your process
crypt-env exec "node app.js"
3๏ธโฃ Environment variables are cleared after the process ends
Thatโs it! No more insecure .env files lying around.
๐ฅ Who Should Use CryptEnv?
๐ก Backend Developers โ Prevent secret leaks in code repositories.
๐ DevOps & Security Engineers โ Improve security posture by eliminating plaintext secrets.
๐ฆ Open Source Contributors โ Keep credentials safe while working in public repositories.
๐ป Anyone Using .env Files โ If youโre using .env, you need CryptEnv.
๐ Get Started Today!
Ready to level up your environment variable security? Try CryptEnv now! ๐
๐ GitHub Repository
If you like this project, consider starring it on GitHub โญ and sharing it with your fellow developers!
Letโs build secure and privacy-focused applications together! ๐
Top comments (1)
nice tool