About
Built out of frustration with watching secrets get pasted into Slack. Again. And again.
Every developer team has the same ritual: a new person joins the project. Someone pastes the .env file into Slack. Or emails it. Or creates a shared Google Doc. The file — containing database passwords, API keys, and payment credentials — now lives in four insecure places instead of one.
Those Slack messages are searchable forever. Slack admins can read them. Bots can read them. Future employees can search for them. A single workspace breach exposes every secret ever shared in that workspace. The industry knows this is wrong, but no tool made it easy to do the right thing.
share-env is a zero-configuration CLI tool that solves this specific problem — and nothing else. It encrypts your .env file with AES-256-GCM on your own machine, uploads only the ciphertext to a temporary relay server, and gives you a one-time share code.
The relay server is architecturally blind: it stores only ciphertext. The decryption key lives only in your share code. The payload is deleted after the first pull. If nobody collects it within 10 minutes, it is automatically destroyed. The relay cannot decrypt what it stores, and nothing persists.
| Encryption | AES-256-GCM (Node.js crypto module) |
| Key size | 256 bits (32 bytes), randomly generated per push |
| IV size | 96 bits (12 bytes), randomly generated per push |
| Auth tag | 128 bits (GCM mode) |
| Language | TypeScript |
| Runtime | Node.js 18+ |
| Distribution | npm (share-env package) |
| License | MIT |
| Relay storage | In-memory (no database) |
| Relay TTL | 600 seconds (10 minutes) |