Your Terminal Remembers Every Secret You've Ever Typed
TL;DR: I built envsec, a free, open-source CLI that stores your development secrets in macOS Keychain, GNOME Keyring, or Windows Credential Manager. Run commands with secrets without ever exposing ...

Source: DEV Community
TL;DR: I built envsec, a free, open-source CLI that stores your development secrets in macOS Keychain, GNOME Keyring, or Windows Credential Manager. Run commands with secrets without ever exposing them in your shell history or ps output. Generate .env files on the fly when you need them, delete them when you're done. No provider, no account, no subscription. The v1.0 beta is out now. npm install -g envsec@beta and you're done. The secrets hiding in your terminal Open your shell history right now. Go ahead, history | grep -i key or history | grep -i password. Scared yet? Every time you run curl with an API key, psql with a connection string, or docker run with credentials, those secrets land in your shell history file. They show up in ps output. They live in plaintext on disk until you manually scrub them — which you never do. And it gets worse. If you're like most developers, you also have .env files scattered across every project directory on your machine — including projects you have