dsh-vault

Vault

用于 DeepSeek Harness 的加密凭据保管库：通过模型工具和设置 UI 页面存储和检索用户名、电子邮箱、电话号码、密码、TOTP 密钥、SSH/API 密钥/OAuth 开发者凭据。

目标 Profile

插件会安装到这里；不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add dsh-vault@1.10.73

兼容性与来源证明

Vault 以 dsh-vault 发布，当前版本为 1.10.73。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。

DSH 兼容范围: *
运行环境: web
发布来源: npm
Registry 更新时间: 2026/9/20

版本

1.10.73stable

2026/9/17

1.10.72stable

2026/9/17

1.10.71stable

2026/9/17

查看其余 259 个版本

← Plugins

dsh-vault

Vault

目标 Profile

插件会安装到这里；不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add dsh-vault@1.10.73

README

dsh-vault — Encrypted Credential Vault for DeepSeek Harness

English | 中文

dsh-vault is a security-focused plugin for DeepSeek Harness that stores sensitive credentials — usernames, emails, phone numbers, passwords, TOTP secrets, and developer credentials like SSH connections, API keys, secrets, and OAuth access/refresh tokens — encrypted at rest, and exposes them to the model through CRUD, search, password generation, and TOTP tools, plus a Settings UI page.

Security & Implementation

Zero external crypto dependencies: everything is built on Node's built-in node:crypto (AES-256-GCM authenticated encryption, scrypt key derivation, RFC 6238 TOTP).
Master password: every entry is encrypted with a 256-bit key derived via scrypt(master password, salt) and AES-256-GCM. The key never touches disk; after unlock it is cached in-process and re-derived on restart.
Tamper-evident: GCM auth tags plus a fixed-plaintext verification envelope — a wrong master password or modified ciphertext fails immediately, never returning garbage.
No plaintext at rest: the on-disk document contains no plaintext credentials; each entry uses an independent random nonce.
Atomic writes: reuses the harness writeFileAtomic + file lock; in-process writes are serialized, cross-process writers take the lock.
Search never leaks: vault_search returns summaries only (id/title/kind/username/email/phone/host/port/url/tags) — never passwords, keys, tokens, or TOTP secrets. Full credentials are readable only via explicit by id.

兼容性与来源证明

Vault 以 dsh-vault 发布，当前版本为 1.10.73。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。

DSH 兼容范围: *
运行环境: web
发布来源: npm
Registry 更新时间: 2026/9/20

版本

1.10.73stable

2026/9/17

1.10.72stable

2026/9/17

1.10.71stable

2026/9/17

查看其余 259 个版本

1.10.70stable

2026/9/17

1.10.69stable

2026/9/16

1.10.68stable

2026/9/16

1.10.67stable

2026/9/16

1.10.66stable

2026/9/16

1.10.65stable

2026/9/16

1.10.64stable

2026/9/16

1.10.64-rc.9prerelease

2026/9/15

1.10.64-rc.8prerelease

2026/9/15

1.10.64-rc.7prerelease

2026/9/15

1.10.64-rc.6prerelease

2026/9/15

1.10.64-rc.5prerelease

2026/9/15

1.10.64-rc.4prerelease

2026/9/15

1.10.64-rc.3prerelease

2026/9/15

1.10.64-rc.2prerelease

2026/9/15

1.10.64-rc.1prerelease

2026/9/15

1.10.63stable

2026/9/15

1.10.63-rc.4prerelease

2026/9/10

1.10.63-rc.3prerelease

2026/9/10

1.10.63-rc.2prerelease

2026/9/10

1.10.63-rc.1prerelease

2026/9/10

1.10.62stable

2026/9/10

1.10.62-rc.1prerelease

2026/9/10

1.10.61stable

2026/9/10

1.10.60-rc.1prerelease

2026/9/10

1.10.59-rc.1prerelease

2026/9/10

1.10.58-rc.1prerelease

2026/9/10

1.10.57-rc.1prerelease

2026/9/10

1.10.56-rc.1prerelease

2026/9/10

1.10.55-rc.1prerelease

2026/9/10

1.10.54-rc.1prerelease

2026/9/10

1.10.53-rc.1prerelease

2026/9/10

1.10.52-rc.1prerelease

2026/9/10

1.10.51-rc.1prerelease

2026/9/10

1.10.50-rc.1prerelease

2026/9/9

1.10.49-rc.1prerelease

2026/9/9

1.10.48stable

2026/9/9

1.10.47-rc.1prerelease

2026/9/8

1.10.46-rc.1prerelease

2026/9/7

1.10.45-rc.1prerelease

2026/9/7

1.10.44stable

2026/9/7

1.10.43-rc.1prerelease

2026/9/7

1.10.42-rc.1prerelease

2026/9/7

1.10.41-rc.1prerelease

2026/9/7

1.10.40-rc.1prerelease

2026/9/7

1.10.39-rc.1prerelease

2026/9/4

1.10.38-rc.1prerelease

2026/9/4

1.10.37-rc.1prerelease

2026/9/4

1.10.36-rc.1prerelease

2026/9/4

1.10.35-rc.1prerelease

2026/9/4

1.10.34stable

2026/9/3

1.10.34-rc.1prerelease

2026/9/3

1.10.33-rc.1prerelease

2026/9/3

1.10.32-rc.1prerelease

2026/9/3

1.10.31-rc.1prerelease

2026/9/3

1.10.30-rc.1prerelease

2026/9/3

1.10.29-rc.1prerelease

2026/9/3

1.10.28-rc.1prerelease

2026/9/3

1.10.27-rc.1prerelease

2026/9/3

1.10.26-rc.1prerelease

2026/9/3

1.10.25-rc.1prerelease

2026/9/3

1.10.24-rc.1prerelease

2026/9/3

1.10.23-rc.1prerelease

2026/9/3

1.10.22-rc.2prerelease

2026/9/3

1.10.22-rc.1prerelease

2026/9/3

1.10.21-rc.1prerelease

2026/9/1

1.10.20stable

2026/9/1

1.10.20-rc.1prerelease

2026/9/1

1.10.19-rc.1prerelease

2026/9/1

1.10.18-rc.1prerelease

2026/9/1

1.10.17-rc.1prerelease

2026/9/1

1.10.16-rc.1prerelease

2026/9/1

1.10.15-rc.1prerelease

2026/9/1

1.10.14-rc.1prerelease

2026/9/1

1.10.13-rc.1prerelease

2026/9/1

1.10.12-rc.1prerelease

2026/9/1

1.10.11-rc.1prerelease

2026/9/1

1.10.10-rc.1prerelease

2026/9/1

1.10.9-rc.1prerelease

2026/8/28

1.10.8-rc.2prerelease

2026/8/27

1.10.8-rc.1prerelease

2026/8/27

1.10.7-rc.1prerelease

2026/8/27

1.10.6stable

2026/8/27

1.10.6-rc.2prerelease

2026/8/27

1.10.6-rc.1prerelease

2026/8/27

1.10.5-rc.1prerelease

2026/8/26

1.10.4-rc.1prerelease

2026/8/26

1.10.3-rc.1prerelease

2026/8/26

1.10.2-rc.2prerelease

2026/8/25

1.10.1-rc.1prerelease

2026/8/24

1.10.2-rc.1prerelease

2026/8/24

1.10.0stable

2026/8/24

1.10.0-rc.2prerelease

2026/8/24

1.10.0-rc.1prerelease

2026/8/24

1.9.9stable

2026/8/24

1.9.9-rc.2prerelease

2026/8/24

1.9.9-rc.1prerelease

2026/8/24

1.9.8stable

2026/8/24

1.9.8-rc.2prerelease

2026/8/24

1.9.8-rc.1prerelease

2026/8/24

1.9.7stable

2026/8/24

1.9.7-rc.1prerelease

2026/8/24

1.9.6stable

2026/8/24

1.9.6-rc.3prerelease

2026/8/24

1.9.6-rc.2prerelease

2026/8/24

1.9.6-rc.1prerelease

2026/8/24

1.9.5stable

2026/8/24

1.9.5-rc.3prerelease

2026/8/24

1.9.5-rc.2prerelease

2026/8/24

1.9.5-rc.1prerelease

2026/8/24

1.9.4stable

2026/8/24

1.9.4-rc.4prerelease

2026/8/24

1.9.4-rc.3prerelease

2026/8/24

1.9.4-rc.2prerelease

2026/8/24

1.9.4-rc.1prerelease

2026/8/24

1.9.3stable

2026/8/24

1.9.3-rc.14prerelease

2026/8/24

1.9.2stable

2026/8/18

1.9.2-rc.1prerelease

2026/8/18

1.9.1stable

2026/8/18

1.9.1-rc.1prerelease

2026/8/18

1.9.0stable

2026/8/18

1.9.0-rc.3prerelease

2026/8/18

1.9.0-rc.2prerelease

2026/8/18

1.9.0-rc.1prerelease

2026/8/18

1.8.1stable

2026/8/18

1.8.1-rc.4prerelease

2026/8/18

1.8.1-rc.3prerelease

2026/8/18

1.8.1-rc.2prerelease

2026/8/18

1.8.1-rc.1prerelease

2026/8/18

1.8.0stable

2026/8/18

1.8.0-rc.2prerelease

2026/8/18

1.8.0-rc.1prerelease

2026/8/18

1.7.1stable

2026/8/18

1.7.1-rc.3prerelease

2026/8/18

1.7.1-rc.2prerelease

2026/8/18

1.7.1-rc.1prerelease

2026/8/18

1.7.0stable

2026/8/18

1.7.0-rc.2prerelease

2026/8/18

1.7.0-rc.1prerelease

2026/8/18

1.6.1stable

2026/8/18

1.6.1-rc.8prerelease

2026/8/18

1.6.1-rc.7prerelease

2026/8/18

1.6.1-rc.6prerelease

2026/8/18

1.6.1-rc.5prerelease

2026/8/18

1.6.1-rc.4prerelease

2026/8/18

1.6.1-rc.3prerelease

2026/8/18

1.6.1-rc.2prerelease

2026/8/18

1.6.1-rc.1prerelease

2026/8/18

1.6.0stable

2026/8/17

1.6.0-rc.10prerelease

2026/8/17

1.6.0-rc.9prerelease

2026/8/17

1.6.0-rc.8prerelease

2026/8/17

1.6.0-rc.7prerelease

2026/8/17

1.6.0-rc.6prerelease

2026/8/17

1.6.0-rc.5prerelease

2026/8/17

1.6.0-rc.4prerelease

2026/8/17

1.6.0-rc.3prerelease

2026/8/17

1.6.0-rc.2prerelease

2026/8/17

1.6.0-rc.1prerelease

2026/8/17

1.5.0stable

2026/8/17

1.5.0-rc.12prerelease

2026/8/17

1.5.0-rc.11prerelease

2026/8/17

1.5.0-rc.10prerelease

2026/8/17

1.5.0-rc.9prerelease

2026/8/15

1.5.0-rc.8prerelease

2026/8/15

1.5.0-rc.7prerelease

2026/8/15

1.5.0-rc.6prerelease

2026/8/15

1.5.0-rc.5prerelease

2026/8/15

1.5.0-rc.4prerelease

2026/8/15

1.5.0-rc.3prerelease

2026/8/15

1.5.0-rc.2prerelease

2026/8/15

1.5.0-rc.1prerelease

2026/8/15

1.4.0stable

2026/8/15

1.4.0-rc.11prerelease

2026/8/15

1.4.0-rc.10prerelease

2026/8/15

1.4.0-rc.9prerelease

2026/8/15

1.4.0-rc.8prerelease

2026/8/15

1.4.0-rc.7prerelease

2026/8/15

1.4.0-rc.6prerelease

2026/8/15

1.4.0-rc.5prerelease

2026/8/15

1.4.0-rc.4prerelease

2026/8/15

1.4.0-rc.3prerelease

2026/8/15

1.4.0-rc.2prerelease

2026/8/15

1.4.0-rc.1prerelease

2026/8/15

1.3.0-rc.9prerelease

2026/8/15

1.3.0stable

2026/8/15

1.3.0-rc.8prerelease

2026/8/15

1.3.0-rc.7prerelease

2026/8/15

1.3.0-rc.6prerelease

2026/8/15

1.3.0-rc.5prerelease

2026/8/15

1.3.0-rc.4prerelease

2026/8/15

1.3.0-rc.3prerelease

2026/8/15

1.3.0-rc.2prerelease

2026/8/15

1.3.0-rc.1prerelease

2026/8/15

1.2.0stable

2026/8/15

1.2.0-rc.9prerelease

2026/8/15

1.2.0-rc.8prerelease

2026/8/15

1.2.0-rc.7prerelease

2026/8/15

1.2.0-rc.6prerelease

2026/8/15

1.2.0-rc.5prerelease

2026/8/15

1.2.0-rc.4prerelease

2026/8/15

1.2.0-rc.3prerelease

2026/8/15

1.2.0-rc.2prerelease

2026/8/15

1.2.0-rc.1prerelease

2026/8/15

1.1.0stable

2026/8/15

1.1.0-rc.4prerelease

2026/8/15

1.1.0-rc.3prerelease

2026/8/15

1.1.0-rc.2prerelease

2026/8/15

1.1.0-rc.1prerelease

2026/8/15

1.0.1stable

2026/8/15

1.0.0stable

2026/8/15

0.9.9stable

2026/8/15

0.9.8stable

2026/8/15

0.9.7stable

2026/8/15

0.9.6stable

2026/8/15

0.9.5stable

2026/8/15

0.9.4stable

2026/8/15

0.9.3stable

2026/8/15

0.9.2stable

2026/8/15

0.9.1stable

2026/8/15

0.9.0stable

2026/8/14

0.8.9stable

2026/8/14

0.8.8stable

2026/8/14

0.8.7stable

2026/8/14

0.8.6stable

2026/8/14

0.8.5stable

2026/8/14

0.8.4stable

2026/8/14

0.8.3stable

2026/8/14

0.8.2stable

2026/8/14

0.8.1stable

2026/8/14

0.8.0stable

2026/8/14

0.7.9stable

2026/8/14

0.7.8stable

2026/8/14

0.7.7stable

2026/8/14

0.7.6stable

2026/8/14

0.7.5stable

2026/8/14

0.7.4stable

2026/8/14

0.7.3stable

2026/8/14

0.7.2stable

2026/8/14

0.7.1stable

2026/8/14

0.7.0stable

2026/8/14

0.6.8stable

2026/8/14

0.6.7stable

2026/8/14

0.6.6stable

2026/8/14

0.6.5stable

2026/8/14

0.6.4stable

2026/8/14

0.6.3stable

2026/8/14

0.6.2stable

2026/8/14

0.6.1stable

2026/8/14

0.6.0stable

2026/8/14

0.5.1stable

2026/8/14

0.5.0stable

2026/8/14

0.4.0stable

2026/8/14

0.3.0stable

2026/8/14

0.2.0stable

2026/8/14

0.1.2stable

2026/8/14

0.1.1stable

2026/8/14

0.1.0stable

2026/8/14

README

dsh-vault — Encrypted Credential Vault for DeepSeek Harness

English | 中文

Security & Implementation

Zero external crypto dependencies: everything is built on Node's built-in node:crypto (AES-256-GCM authenticated encryption, scrypt key derivation, RFC 6238 TOTP).
Master password: every entry is encrypted with a 256-bit key derived via scrypt(master password, salt) and AES-256-GCM. The key never touches disk; after unlock it is cached in-process and re-derived on restart.
Tamper-evident: GCM auth tags plus a fixed-plaintext verification envelope — a wrong master password or modified ciphertext fails immediately, never returning garbage.
No plaintext at rest: the on-disk document contains no plaintext credentials; each entry uses an independent random nonce.
Atomic writes: reuses the harness writeFileAtomic + file lock; in-process writes are serialized, cross-process writers take the lock.
Search never leaks: vault_search returns summaries only (id/title/kind/username/email/phone/host/port/url/tags) — never passwords, keys, tokens, or TOTP secrets. Full credentials are readable only via explicit by id.

vault_get

Field	Description
`kind`	`login` (default) / `ssh` / `api-key` / `secret` / `oauth` / `custom`
`username` / `email` / `phone`	Account identity
`password`	The password
`host` / `port`	SSH host and port (e.g. `db.internal` / `2222`)
`privateKey`	SSH private key (PEM)
`apiKey`	API key
`secret`	Generic secret (client secret, shared secret, …)
`accessToken` / `refreshToken` / `expiresAt`	OAuth token pair and expiry (epoch millis)
`otpSecret`	TOTP secret (bare Base32 or otpauth:// URI)
`url` / `notes` / `tags`	Metadata
`fields`	Arbitrary key/value pairs (e.g. `{"region": "us-east-1"}`), searchable

Tool	Purpose
`vault_add`	Add an entry (any combination of fields; empty strings/arrays are ignored)
`vault_get`	Read a full entry by id (including all secrets)
`vault_search`	Search titles/categories/usernames/emails/phones/hosts/ports/URLs/notes/tags/custom fields (incl. numeric/boolean/nested values; whitespace-separated terms OR-match); optional `createdAfter`/`createdBefore` epoch-millis filters; returns secret-free summaries; `limit` must be an integer 1–100
`vault_update`	Update fields by id (unprovided fields kept; empty string clears a field; `title` is renamable; `rotationDays: 0` clears rotation = never rotate)
`vault_compare`	Compare two entries field by field (`onlyA`/`onlyB`/`differ`/`equal`) — field names only, never secret values
`vault_rename`	Rename an entry in one call (shortcut for `vault_update`)
`vault_delete`	Soft-delete an entry (moves it to the trash, still encrypted on disk)
`vault_restore` / `vault_purge` / `vault_restore_recent`	Bring a trashed entry back / purge it / undo the last delete
`vault_lock` / `vault_unlock`	Explicitly lock the vault (wipe the in-memory key) / re-unlock it
`vault_totp`	Generate the current 6-digit code for a stored otpSecret (or a bare Base32 / otpauth URI)
`vault_generate_password`	Generate a strong random password (length/classes/grouping) or a memorable passphrase (`passphrase: true`, EFF-style word list, `words`/`separator`/`wordDigits`)
`vault_strength`	Zero-dependency password strength estimate (score 0–100, weak/fair/strong/very strong)
`vault_password_history`	List an entry's previous passwords (1Password/Bitwarden-style, newest first, capped at 10; current password excluded)
`kind: card`	Bank/credit-card entries: `cardNumber`/`cardExpiry` (MM/YY)/`cardCvv`/`cardHolder`; search summaries expose expiry + holder only (never the number or CVV); Bitwarden JSON export maps to a `card` item (type 3, brand inferred)
`vault_password_rollback`	Restore an entry password to a stored history entry (current password is archived first, so it is reversible)
`vault_recovery_code` / `vault_verify_recovery` / `vault_recovery_status`	One-time vault recovery code (1Password/Bitwarden-style): 32-char code shown once, only its SHA-256 hash is stored; verify possession of the code; check whether one is set
`vault_rekey`	Upgrade the vault to fresh scrypt KDF parameters in place
`vault_backup`	Timestamped encrypted backup with retention; optional `note`
`vault_import_csv`	Bulk-import credentials from a CSV file (custom columns become fields; `overwrite: true` merges fields into existing entries instead of duplicating)
`vault_bulk_delete`	Soft-delete entries matching a query/kind/tag or explicit ids; `confirm: true` required (dry-run by default); trashed entries are restorable
`vault_apply_tags`	Bulk add/remove/replace tags on every entry matching a query (dry-run supported, no secrets)
`vault_totp_uri`	Build an otpauth:// provisioning URI for a stored or bare TOTP secret
`vault_switch` / `vault_list`	Switch the active vault by name / list available vaults
`vault_rotation`	Report expired / due-for-rotation / expiring-soon credentials; `soonWindowDays` (1-90, default 7) tunes the soon horizon (no secrets)
`vault_health`	Vault health scan: weak/reused passwords, missing 2FA, insecure http:// sites, and an overall security score (0–100)
`vault_watchtower`	Watchtower-style per-entry risk analysis (1Password/Bitwarden-inspired): flags short/weak passwords, keyboard sequences, embedded years, common passwords, reuse, http:// sites, missing 2FA, expiry — with a 0–100 score and good/warn/poor verdict (no secrets); entry rows show ⚠ badges
`vault_breach_check`	Watchtower-style breach scan against Have I Been Pwned (k-anonymity: only the SHA-1 prefix leaves the machine), with an offline common-password fallback
`vault_integrity`	Verify the on-disk vault file decrypts correctly and matches the in-memory store
`vault_merge`	Merge one entry into another; `keepSource: true` keeps the source after merging
`vault_attach` / `vault_attachments` / `vault_attachment` / `vault_detach`	Attach files to entries (private keys, certs, configs, recovery codes) — stored base64 inside the encrypted entry, encrypted at rest; list names/sizes, read content, remove
`vault_quick_add`	Fast capture (title + one secret) with optional tags/notes
`vault_expiry`	Set/clear expiry (`expiresAt: 0` removes it)
`vault_stats`	Overview counts incl. `trashCount` (no secrets)
`vault_verify`	Verify one entry or audit every entry (`all: true`) for per-kind completeness, port/expiry sanity (no secrets)
`vault_duplicates`	Find duplicate groups: `mode` = `both` (default) / `title` / `content` (no secrets)
`vault_report`	Printable inventory with expiry/rotation columns and a stats footer (no secrets)
`vault_export` / `vault_import`	Portable encrypted backup/migration of the whole vault (separate export password)
`vault_backup` / `vault_backup_now`	Timestamped encrypted backup named `<vault>-backups-YYYY-MM-DD_HH-MM-SS-<hex>.json` (owning vault + date visible); retention pruning keeps the newest N
`vault_restore_backup`	Restore from a backup: `mode: "merge"` (default) copies the backup entries INTO the current vault so they appear in the entries list; `mode: "replace"` overwrites the whole vault with a safety snapshot first
`vault_vault_rename` / `vault_vault_delete`	Rename a named vault (file moves, active session follows) or permanently delete one (default vault protected)
`vault_match_url`	Find login entries matching a URL (Bitwarden/1Password-style: exact host, subdomain, parent domain, path-prefix; www./port normalization) with a 0–100 score — never returns the password
`vault_fill`	Find the entry matching a host/URL/username/title and return its credentials
`vault_env`	Render env-flagged entries (tags contain `env`) as `KEY=VALUE` lines — see Environment export
`vault_export_bitwarden` / `vault_import_bitwarden`	Bitwarden/Vaultwarden JSON interop (full field mapping, overwrite support)
`vault_import_bitwarden_encrypted`	Decrypt a Bitwarden password-protected JSON export (PBKDF2/Argon2id + HKDF → AES-256-CBC + HMAC) and import it; pass the export passphrase
`vault_import_manager_csv`	Password-manager CSV auto-detected by header: Bitwarden (`login_uri`/`login_username`/…), 1Password 8, Dashlane, NordPass, Keeper, LastPass (`fav`/`grouping`/`extra`); dryRun preview
`vault_import_kdbx`	KeePass KDBX: 3.1 and 4.x, AES-KDF or Argon2 (RFC 9106), AES-256-CBC or ChaCha20 payload, keyfile support
`vault_export_1password`	Export entries as a 1Password 1PUX archive (ZIP + export.data) for import into 1Password or re-import here; item categories map to login / credit card / API credential / server
`vault_import_1password` / `vault_import_1pif`	1Password 1PUX (ZIP) and legacy 1PIF text exports
`vault_import_enpass`	Enpass JSON export (folders → tags, typed fields, TOTP)
`vault_import_keepass_xml`	KeePass 2.x XML export (plaintext or `********` masked values)
`vault_import_chrome` / `vault_import_keychain`	Import passwords from Chrome's Login Data (macOS keychain / Linux keyring or `peanuts` / Windows DPAPI) or the macOS Keychain (internet passwords `inet` by default — the ones that actually back website logins — or generic `genp` via `classes`; session cache + preview, no prompt spam); every file import supports `dryRun` preview
`vault_import_firefox`	Firefox profile import (logins.json + key4.db, NSS 3DES / PBES2-AES, primary-password aware)
`vault_search_system`	Search Chrome / Keychain for sites & usernames — never exposes passwords
`vault_session_open`	Open a real headed browser window at a URL so the user can log in manually (password, 2FA, captcha) — the portable way to capture login state for sites that block embedding
`vault_session_collect`	Collect every cookie of an open browser session (incl. HttpOnly) and save it as a `cookie` entry
`vault_session_import`	Save session cookies from pasted JSON (devtools export shape) or a raw `Cookie` header string — the no-browser alternative
`vault_session_import_file`	Import a Netscape cookie-jar file (curl `-b` / wget / browser-extension export; the same format `vault_session_export` writes)
`vault_session_list`	List saved login sessions with cookie counts, expired and expiring-in-7d counts (no values)
`vault_session_export`	Export a saved session as a `Cookie` header value, a Netscape cookie-jar file (curl `-b`), raw JSON (Playwright `addCookies` shape), or a ready-to-run Playwright snippet
`vault_session_close`	Close an open browser login session (collected cookies stay in the vault)
`vault_session_prune`	Remove expired cookies from a saved session (session cookies are kept); `preview: true` reports without writing
`vault_copy`	Copy an entry (secrets included) into another named vault
`vault_templates`	Built-in + user-defined templates (save/list/remove), KeePassXC-style; built-ins now include Wi-Fi, Server, Database, Identity, Bank account, Card (1Password-inspired)

Path	Command	Build needed	`allowBuilds`
npm	`add dsh-vault`	no (prebuilt `lib/`)	no
GitHub	`add github:Ox0400/dsh-vault#v0.1.1`	yes (`prepare`)	yes (first run)
local path	`add /abs/path/to/dsh-vault`	no (link to built source)	no
tarball	`add ./dsh-vault-0.1.1.tgz`	no (prebuilt `lib/`)	no

dsh plugin --profile web add dsh-vault

export DSH_VAULT_PASSWORD='your strong master password'

dsh plugin --profile web add github:Ox0400/dsh-vault#v0.1.1

Run the add command — it fails with an allowBuilds error and prints the exact key to allow (the line containing the repo URL, including the resolved commit hash):
```
allowBuilds:
  dsh-vault@https://codeload.github.com/Ox0400/dsh-vault/tar.gz/<sha>: true
```

Append that exact key to the profile's pnpm-workspace.yaml ($DSH_HOME/profiles/<name>/pnpm-workspace.yaml):

packages:
  - .
allowBuilds:
  dsh-vault@https://codeload.github.com/Ox0400/dsh-vault/tar.gz/<sha>: true

Re-run the add — pnpm now runs the prepare script, builds lib/, and installs.

dsh plugin --profile web add /absolute/path/to/dsh-vault

npm pack && dsh plugin --profile web add ./dsh-vault-0.1.1.tgz

your setup	the command
source checkout (`git clone` + `pnpm build`)	`pnpm vault` — or `node lib/cli.js`, or `./lib/cli.js`
plugin installed into a profile	`pnpm dsh plugin --profile web exec dsh-vault`
globally installed (`npm i -g dsh-vault`)	`dsh-vault`
nothing installed	`npx dsh-vault`

# source checkout — this repository, right now:
pnpm vault list

# after a global install (or via npx) the same commands are:
dsh-vault list
npx dsh-vault list

$ dsh-vault env
DEMO_API_KEY='sk-demo-123'
OTHER_PASSWORD='pw-not-exported'

eval "$(dsh-vault env)"          # KEY=VALUE lines become shell variables
echo "$DEMO_API_KEY"

name	what it is	meaning
`env`	an entry tag	which entries `dsh-vault env` exports; nothing is exported without it
`env`	the command	prints exactly the entries carrying that tag
`envKeys`	an entry field (optional)	pin exact names, e.g. `["DASHSCOPE_API_KEY"]`; the old singular `envKey` is accepted as a one-element shorthand

dsh-vault list                             # grouped: what `env` exports vs the rest
#   Exported by `env` (tag "env") — 1 entry:
#     a1b2c3d4-…  api-key   DASHSCOPE        → DASHSCOPE_API_KEY
#   Not exported (no "env" tag) — 1 entry; `get <name>` still works for it:
#     9f8e7d6c-…  api-key   Example Billing  → EXAMPLE_BILLING_API_KEY
dsh-vault get my-entry                     # the entry's primary secret, stdout only
dsh-vault get my-entry --field apiKey      # one named field
dsh-vault get my-entry --mask              # confirm it exists without printing it
dsh-vault show my-entry                    # non-secret metadata as JSON
dsh-vault env                              # env-tagged entries as KEY=VALUE
dsh-vault env --mask                       # human view, both sections as KEY=VALUE:
#   ## exported items
#   NPM_REGISTRY_API_KEY=npm_***
#   ## unexported items
#   EXAMPLE_BILLING_API_KEY=***
dsh-vault export-env .env                  # …or write them to a 0600 file
dsh-vault verify                           # check the master password, nothing on stdout

$ export $(dsh-vault env); echo "$WITH_SPACE"
['pass]                     # split at the space
bash: export: `here': not a valid identifier
$ eval "$(dsh-vault env)"; echo "$WITH_SPACE"
[pass word here]            # read as intended

dsh-vault export-env .env && set -a && . ./.env && set +a

DSH_VAULT_MASTER_PASSWORD=… pnpm vault list
printf '%s\n' "$PASSWORD" | pnpm vault list --password-stdin

git clone git@github.com:Ox0400/dsh-vault.git && cd dsh-vault
npm install && npm run build            # builds lib/, including executable lib/cli.js

pnpm vault list                         # the repo's own entry point (package.json script)
node lib/cli.js list                    # same thing, spelled out
./lib/cli.js list                       # the file is executable too
npm link                                # …or put a real `dsh-vault` on PATH

ln -sf ../dsh-vault/lib/cli.js ~/.dsh/profiles/web/node_modules/.bin/dsh-vault

pnpm dsh plugin --profile web add dsh-vault          # into a profile (plugin + CLI together)
pnpm dsh plugin --profile web exec dsh-vault list    # --profile is required

npm i -g dsh-vault && dsh-vault list                 # globally
npx dsh-vault list                                   # or not at all

GET https://api.pwnedpasswords.com/range/<FIRST 5 HEX CHARS OF SHA-1(password)>
Add-Padding: true

Entry	Exported key
title `DASHSCOPE`, `apiKey`	`DASHSCOPE_API_KEY`
title `DASHSCOPE`, `prefix: APP_`	`APP_DASHSCOPE_API_KEY`
`envKey: "TAVILY_TOKEN"`, `accessToken`	`TAVILY_TOKEN`
…the same entry's `refreshToken` / `fields.scope`	`TAVILY_TOKEN_REFRESH_TOKEN` / `TAVILY_TOKEN_SCOPE`

The field suffix is vendor-standard: apiKey → API_KEY, accessToken → ACCESS_TOKEN, refreshToken → REFRESH_TOKEN, privateKey → PRIVATE_KEY, password → PASSWORD, cardNumber → CARD_NUMBER.

Set an entry's env-var names (optional field envKeys, also via vault_add/vault_update, or comma-separated in the editor) when the derived names are not what your scripts expect. They are positional and used verbatim (no prefix, no title):

`envKeys`	exported
`["DASHSCOPE_API_KEY"]`	`DASHSCOPE_API_KEY=apiKey`
`["GOOGLE_ACCESS_TOKEN", "GOOGLE_REFRESH_TOKEN"]`	`...=accessToken`, `...=refreshToken`
`["MY_KEY"]` on an entry with 3 secrets	`MY_KEY`, `MY_KEY_REFRESH_TOKEN`, `MY_KEY_SCOPE`

Each name must be a POSIX identifier ([A-Za-z_][A-Za-z0-9_]*), at most 8, and no duplicates. envKey (singular string) is still accepted as a one-element shorthand and is folded into envKeys on write.

Custom fields are exported too, as <BASE>_<FIELD>.

Profile	Registers
Basic (default)	core only — everyday use
Standard	+ management: favourites, tags, icons, expiry/rotation, health, duplicates/merge, attachments, templates, env masks
Full	everything, incl. bulk import/export, browser sessions, backups and vault-file operations
Custom…	core + any of: Management / Import-export / Browser sessions / Backups & files

[!WARNING] Security: never put the master password in plaintext A profile patch (cordis.patch.yml / cordis.yml) is a config file that is easy to commit to git, screenshot, or capture in logs — so a plaintext masterPassword: row leaks the key to your whole encrypted vault. Always use masterPasswordEnv and export the real password into the process/shell environment instead (e.g. export DSH_VAULT_PASSWORD='…'). See the community-plugin-audit handbook for the evidence-first checklist for credential-handling plugins.
# ✗ DON'T — plaintext master password in a config file
- id: vault
  name: dsh-vault
  config:
    masterPassword: 'my-secret'
# ✓ DO — reference an environment variable; keep the file itself 0600
- id: vault
  name: dsh-vault
  config:
    masterPasswordEnv: DSH_VAULT_PASSWORD

Option	Description
`masterPassword`	The master password inline (appears in cordis.yml; not recommended)
`masterPasswordEnv`	Environment variable name holding the master password (recommended)
`path`	Vault file path; defaults to `$DSH_HOME/vault/default.json`
`name`	Vault name for the default path (e.g. `name: work` → `$DSH_HOME/vault/work.json`)
`accessMode`	Access policy for the model tools. Three states: `readonly` (mutations rejected on tools + UI), `ask` (default — reads free, every add/update/delete goes through the harness approval channel so the user confirms each write), or `auto` (automatic read-write, no per-call prompt). The Settings UI offers this exact three-way choice and persists it to `<vault dir>/access.json`.
`autoCapture`	`false` (default). When `true`, the system prompt instructs the model to detect credentials shared in conversation and — per user preference — offer to save them with `vault_add`.
`lockTimeoutSeconds`	Auto-lock: after this many seconds of inactivity the vault re-locks (key wiped) and every read/write requires `vault_unlock`. `0`/absent disables.
`exportPasswordEnv`	Environment variable holding the export/import password for `vault_export`/`vault_import` (never pass it as a model argument).
`backupRetention`	How many encrypted backups to keep (default 10); `vault_backup` prunes older copies.

- id: vault
  name: dsh-vault
  config:
    masterPasswordEnv: DSH_VAULT_PASSWORD
    accessMode: ask
    autoCapture: true

git clone git@github.com:Ox0400/dsh-vault.git
cd dsh-vault
pnpm install    # installs devDependencies (typescript/tsdown/vitest, …)
pnpm build      # builds host lib/*.js and the browser bundle lib/client.js
pnpm test       # runs the 420 vitest tests

pnpm test          # unit + integration tests (vitest, 420)
pnpm typecheck     # tsc -p tsconfig.json --noEmit
pnpm build         # = build:host (tsc) + build:client (tsdown)
npm pack           # optional: tarball for `dsh plugin add ./dsh-vault-0.1.1.tgz`

node tests/e2e/theme-check.mjs      # dual-theme tokens, ring track, attach row
node tests/e2e/polish-check.mjs     # empty-state copy, relative-age hover hints
node tests/e2e/contrast-audit.mjs   # WCAG sweep over all eight tabs, both themes

--v-text: var(--dsw-alias-label-primary, #1f2328);
--v-border: var(--dsw-alias-border-l2, #d9d9d9);
--v-success-text: color-mix(in srgb, var(--v-success) 55%, var(--v-text));

npm pack                  # tarball → dsh plugin add ./dsh-vault-0.1.1.tgz
npm publish --access public   # registry → dsh plugin add dsh-vault

score	filled stars	band
0–8	0	weak
9–24	½	weak
25–41	1	weak
42–58	1½	fair
59–74	2	fair
75–91	2½	strong
92–100	3	very strong

Vault

兼容性与来源证明

版本

Vault

README

dsh-vault — Encrypted Credential Vault for DeepSeek Harness

Security & Implementation

兼容性与来源证明

版本

README

dsh-vault — Encrypted Credential Vault for DeepSeek Harness

Security & Implementation

Entry Model

Tools

Installation

Option 1: Install from npm (easiest)

Option 2: Install from GitHub (pin a tag or commit)

Option 3: Install from a local path

Option 4: Install from a tarball

Command line

0. First: which command can you actually type?

1. What `env` is for

2. The commands

3. Shell quoting: not `export $(…)`

4. The master password

5. Install details

Privacy of the breach check

Strength indicator

Environment export

Tool profiles

Configuration

Development

Keeping credentials out of public content

Theming

Packaging & Publishing

Security Boundaries & Known Limitations

Listed in

Vault

兼容性与来源证明

版本

Vault

README

dsh-vault — Encrypted Credential Vault for DeepSeek Harness

Security & Implementation

兼容性与来源证明

版本

相关插件

相关插件

README

dsh-vault — Encrypted Credential Vault for DeepSeek Harness

Security & Implementation

Entry Model

Tools

Installation

Option 1: Install from npm (easiest)

Option 2: Install from GitHub (pin a tag or commit)

Option 3: Install from a local path

Option 4: Install from a tarball

Command line

0. First: which command can you actually type?

1. What env is for

2. The commands

3. Shell quoting: not export $(…)

4. The master password

5. Install details

Privacy of the breach check

Strength indicator

Environment export

Tool profiles

Configuration

Development

Keeping credentials out of public content

Theming

Packaging & Publishing

Security Boundaries & Known Limitations

Listed in

相关插件

1. What `env` is for

3. Shell quoting: not `export $(…)`