Hashicorp Vault
@jamesakeech/hashicorp-vaultv2026.11.14.1
01README
HashiCorp Vault secrets management via REST API (KV v1 and v2). Emits OpenTelemetry spans for get, put, and list, with one child span per request in the recursive list walk, so vault reads are visible in traces including reads during model and workflow runs where the host emits nothing. Span attributes carry the vault name, key name, and KV version only — never secret values, tokens, or error messages.
02Vaults
HashiCorp Vaultconfigurable
@jamesakeech/hashicorp-vaultextensions/vaults/hashicorp.ts
HashiCorp Vault secrets management via REST API
Config Fields
| Field | Type | Description |
|---|---|---|
| address | string | Vault server address (e.g., https://vault.example.com:8200) |
| token? | string | Vault authentication token. Leave this unset and run `vault login`, which |
| tokenFile? | string | Path to an OpenBao Agent or Vault Agent token sink. Read before every |
| mount? | string | Secrets engine mount path |
| kvVersion? | enum | KV secrets engine version |
| namespace? | string | Vault namespace (Enterprise only) |
03Stats
A
100 / 100
Downloads
51
Archive size
21.9 KB
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Docs keep secrets in a vault1/1earned
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License2/2earned
- Verified public repository2/2earned
credentials-sensitive-field1 accepted
A field that looks like a secret but is not marked sensitive, so its value is not vaulted.
- vaults/extensions/vaults/hashicorp.ts:42 — file path only; the token remains in the Agent sink.
05Platforms
06Labels