Skip to content
Back to search

envault

A local, minimum, encrypted secrets vault for coding agents — let your AI works with your keys and secret, but never sees them.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mildynora--envault/badge.svg)](/listings/mildynora--envault)

HTML

<a href="/listings/mildynora--envault"><img src="/api/listings/mildynora--envault/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

**Homebrew (macOS / Linux):**

brew install MildyNora/envault/envault

**Or the no-Rust install script** — it also creates your vault and sets up the skill:

curl -fsSL https://raw.githubusercontent.com/MildyNora/envault/master/install.sh | bash
# Windows (PowerShell)
irm https://raw.githubusercontent.com/MildyNora/envault/master/install.ps1 | iex

**Or from source** (needs [Rust](https://rustup.rs)):

git clone https://github.com/MildyNora/envault.git && cd envault && ./install.sh

Then run **`envault`** to open the dashboard (it offers to create your vault on first launch); `envault skill install` sets up your agents. Works on macOS, Windows, and Linux.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 12 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "envault",
  3. "description": "envault: local secrets vault for agentic coding — agents see aliases and ciphers, never plaintext.",
  4. "owner": { "name": "purifido" },
  5. "plugins": [
  6. {
  7. "name": "envault",
  8. "source": "./plugin",
  9. "description": "Secrets vault workflow for agents: aliases and ciphers only, never plaintext."
  10. }
  11. ]
  12. }
README.md · README · 125 lines · 2 findings marked

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. # Envault
  3. **A local, minimal encrypted secrets vault for coding agents — let your AI work with your keys and secrets without ever seeing them.**
  4. ![License](https://img.shields.io/badge/license-MIT-blue.svg)
  5. ![Platform](https://img.shields.io/badge/platform-macOS%20%7C%20Windows%20%7C%20Linux-lightgrey)
  6. ![Built with Rust](https://img.shields.io/badge/built%20with-Rust-orange)
  7. ![Status](https://img.shields.io/badge/status-beta-yellow)
  8. <b>English</b> · <a href="README.zh-CN.md">简体中文</a>
  9. <br/>
  10. <img src="docs/dashboard.png" alt="the envault dashboard — an interactive, encrypted secrets vault" width="860">
  11. </div>
  12. ---
  13. Store your API keys, tokens, and passwords once. Your coding agent refers to them
  14. **by name** and runs commands through envault — the plaintext only ever exists
  15. inside the process envault launches, never in the model's context, a `.env`, or
  16. your chat history.
  17. > The only one command **you** run is **`envault`** — it opens the dashboard above,
  18. > where you add keys and change settings. Every other `envault …` command below
  19. > (`run`, `link`, `request`, …) is written by your **coding agent**, which learns
  20. > them from the skill envault installs. You rarely type them yourself.
  21. ## Install
  22. **Homebrew (macOS / Linux):**
  23. ```bash
  24. brew install MildyNora/envault/envault
  25. ```
  26. **Or the no-Rust install script** — it also creates your vault and sets up the skill:
  27. ```bash
  28. curl -fsSL https://raw.githubusercontent.com/MildyNora/envault/master/install.sh | bash
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 44 on GitHub
  29. ```
  30. ```powershell
  31. # Windows (PowerShell)
  32. irm https://raw.githubusercontent.com/MildyNora/envault/master/install.ps1 | iex
  33. ```
  34. **Or from source** (needs [Rust](https://rustup.rs)):
  35. ```bash
  36. git clone https://github.com/MildyNora/envault.git && cd envault && ./install.sh
  37. ```
  38. Then run **`envault`** to open the dashboard (it offers to create your vault on
  39. first launch); `envault skill install` sets up your agents. Works on macOS,
  40. Windows, and Linux.
  41. ## 👤 For you — the dashboard
  42. Run **`envault`**. Everything is inside the TUI (shown above): add and edit
  43. secrets, toggle **Touch ID** and the **audit log**, and **rotate** your keypair —
  44. no commands to memorize. Changing a setting or rotating is gated behind Touch ID /
  45. Windows Hello, so an agent can't do it in your place.
  46. ## 🤖 For your agents - they see ciphers
  47. Your agent only ever sees **names and age-encrypted ciphers**. It maps a name to
  48. an environment variable and runs your command through envault, which injects the
  49. real value and **masks it out of the output**:
  50. ```console
  51. $ envault link OPENAI_API_KEY openai
  52. $ envault run -- python app.py # value injected · output masked
  53. ```
  54. When it needs a key you haven't stored, it would not ask you to paste it into chat —
  55. it **requests** a window opens for you:
  56. <p align="center">
  57. <img src="docs/request.png" alt="the envault request window — you grant a secret to the agent without it ever seeing the value" width="720">
  58. </p>
  59. You paste it once (the agent never sees it) or decline. `envault skill install`
  60. teaches this workflow to Claude Code, Codex, and opencode. Or you can manually set up the keys and tell the agent their names.
  61. <details>
  62. <summary><b>The commands your agent runs</b> — you don't need these</summary>
  63. | Command | What it does |
  64. |---|---|
  65. | `envault ls --json` | list secret **names** (never values) |
  66. | `envault link <VAR> <name>` | map an env var to a name |
  67. | `envault run -- <cmd>` | run with secrets injected + output masked |
  68. | `envault request <name>` | ask you for a secret it doesn't have |
  69. | `envault fill <name>` | type a secret into a browser field (opt-in) |
  70. | `envault import <.env>` | encrypt a dotenv file into the vault |
  71. </details>
  72. ## How it works
  73. <p align="center">
  74. <img src="docs/architecture.svg" alt="envault architecture: a trusted zone (you + OS keychain) and an untrusted coding-agent zone, with the numbered data flow through the vault" width="520">
  75. </p>
  76. Secrets are [age](https://age-encryption.org)-encrypted; the private key lives in
  77. your **OS keychain** and never touches disk in the clear. Full design and threat
  78. model: [`docs/how-it-works.md`](docs/how-it-works.md).
  79. ## Scope & the honest boundary
  80. envault keeps secrets **out of your agent's context and your files** — the
  81. prompt-leak and accidental-exposure threat. It is **not a runtime sandbox**: In a very rare case a genuinely malicious process running as *you* can still use a secret through `envault run`, and a fully compromised machine can halt the audit log. If that's your threat model, you need OS-level isolation. Details in [SECURITY.md](SECURITY.md).
  82. ## Contributing
  83. Issues and PRs welcome — see [CONTRIBUTING.md](CONTRIBUTING.md). Found a
  84. vulnerability? Please **don't** open a public issue — [SECURITY.md](SECURITY.md).
  85. ## License
  86. [MIT](LICENSE) · beta — verify the keychain / biometric paths on your own hardware.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.