Stop committing
your secrets.
Ditch .env. Keep your flow.
How it works
Three steps. Zero secrets on disk.
Whether you start from a local file or a cloud vault, the workflow is the same.
Import your .env
Point inject at your existing .env file to encrypt and store it locally.
Run your usual command
inject wraps your process. Secrets load into memory and your command runs as normal.
Delete your .env
No plaintext files on disk. Secrets live only in the process tree and vanish when it exits.
Features
Why inject?
Everything your .env does, without the .env.
Secrets stay in memory
inject wraps your process. Secrets pass through OS environment inheritance and vanish when the terminal closes.
Your vault, your auth
1Password and Bitwarden integration through their existing CLI sessions. No new accounts, tokens, or sync tools.
Your commands don’t change
After setup, npm run dev still works. inject binds to your existing scripts.
Security Model
Eliminate the #1 cause of leaked credentials.
No plaintext .env files on developer laptops, ever.
Before inject
Secret Provider
1Password · Bitwarden
Developer copies
manual copy-paste
.env file on disk
plaintext secrets exposed
Process reads .env
npm run dev · any command
After inject
Secret Provider
1Password · Bitwarden
inject (Memory)
secrets injected via process env
Process
npm run dev · any command
- >Secrets live exclusively in process memory
- >Zero footprint on the filesystem
- >Automatic cleanup on process exit
- >Auditable vault access via existing toolchain