sharenv 🔐

A zero-dependency Node.js CLI to encrypt and share .env files securely.

🔒 Privacy First: Your encryption passkey never leaves your machine. Only the encrypted ciphertext is stored on the server.

📦 Installation

Install globally via npm to use the sharenv command anywhere:

npm install -g sharenv

Or use it without installing via npx:

npx sharenv <command>

🚀 Usage

📤 1. Share a .env file

Navigate to your project folder (or provide a path) and run:

sharenv set

What happens:

1. You'll be prompted for a Passkey. (Choose a strong one!)
2. You can optionally set TTL (how many minutes until the link expires) and Max Reads (how many times it can be downloaded).
3. The CLI encrypts your .env locally using AES-256-GCM.
4. The encrypted blob is uploaded, and you get a Share ID.

Example:

sharenv set ./my-awesome-project

📥 2. Receive a .env file

Run this command with the Share ID provided by the sender:

sharenv get <SHARE_ID>

What happens:

1. The CLI fetches the encrypted data.
2. It prompts you for the Passkey.
3. It decrypts the data locally and saves it as a .env file in your current folder.

📊 3. Check Status

Want to see if a link is still active without "consuming" a read? Use the info command:

sharenv info <SHARE_ID>

🛡️ Security Details

We take security seriously. All operations follow these standards:

• Encryption: AES-256-GCM (Industry standard).
• Key Derivation: PBKDF2-SHA256 with 310,000 iterations (Highly resistant to brute-force).
• Local-Only: Encryption and decryption happen in your terminal. The server only sees random-looking data.
• Auto-Delete: Links are automatically destroyed once they reach their read limit or expiration time.
• Compatibility: Fully compatible with the envsecure.github.io web interface.

🛠️ Requirements

• Node.js: v18.0.0 or higher.
• Zero Dependencies: This CLI is lightweight and uses only native Node.js modules.

📄 License

MIT