Ox0400/dsh-vault

Name: Ox0400/dsh-vault
Author: Ox0400

Plugin插件 Native原生 ⭐ 11 MIT Search & Web Access搜索与联网 Approval & Security审批与安全

DeepSeek Harness 的加密凭据保险库——AES-256-GCM + TOTP，模型工具 + 设置界面

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

dsh-vault is a security-focused encrypted credential vault built natively for DeepSeek Harness. It stores a wide range of sensitive credentials, including usernames, passwords, SSH private keys, API keys, OAuth tokens, and TOTP secrets, all encrypted at rest. It exposes a full set of tooling for DeepSeek Harness agents to manage credentials, including CRUD operations, search, password generation, and TOTP code generation, plus a theme-aware settings UI that matches DeepSeek Harness's styling. It is packaged as an npm package that can be installed directly via the DSH plugin CLI, either from the public npm registry or a local tarball.

This plugin is intended for DeepSeek Harness users that regularly work with multiple sensitive credentials and want to keep them stored inside their DSH environment. It eliminates the need to switch to an external password manager when working inside DSH, keeping all workflow contained within the agent environment. Users set a master password to encrypt the vault, after which the encryption key stays cached in memory until the vault is explicitly locked or DSH restarts. Credential search only returns non-sensitive metadata summaries to the agent, so secrets never leak accidentally. Full credentials are only sent to the agent when a user explicitly retrieves a specific entry by ID.

dsh-vault is released under the open-source MIT license, and has no external cryptographic dependencies of any kind. All encryption functionality is built on Node.js’s built-in node:crypto module, using AES-256-GCM encryption and scrypt key derivation per industry standards. The strength of the vault is directly tied to the strength of the user’s master password, and users are recommended to use a 16+ character high-entropy password for best security. Currently, the plugin is designed exclusively for personal, single-machine DSH deployments, and does not support team-shared vault or multi-user collaboration use cases.

dsh-vault 是专为 DeepSeek Harness 开发的原生加密凭据保险库插件，用于安全存储各类敏感凭据，包括账号信息、密码、API 密钥、SSH 连接凭证、TOTP 密钥等各类开发常用的保密数据。所有凭据采用端到端加密存储，提供增删改查、搜索、密码生成、TOTP生成工具和配套的设置UI页面。

针对 DeepSeek Harness 上需要处理大量敏感凭据的开发用户，这个插件可以帮助用户把所有敏感信息统一管理，不用分散存储在不同文档或第三方密码管理器中。模型可以通过插件提供的工具访问凭据，搜索时只会返回元数据摘要，不会泄露敏感内容，只有显式获取具体条目才会返回完整凭据。

该插件使用 MIT 许可证开源，不依赖外部加密库，全部加密功能基于 Node.js 内置的 crypto 模块实现，主密码强度决定了整体安全性，建议使用长度不低于 16 位的高熵主密码。插件仅针对个人单部署场景设计，不支持团队共享保险库功能，可通过 npm 直接安装到 DSH。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-vault（Ox0400/dsh-vault）
仓库：https://github.com/Ox0400/dsh-vault
本站详情页：https://www.yhbd.top/plugins/ox0400-dsh-vault/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 11 · 最近提交 2026-09-30 · 主语言 TypeScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 note1 项提示

11 stars - an early-stage project星标 11，属于早期项目

DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装

dsh plugin --profile web add dsh-vault

把 Ox0400/dsh-vault 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

37.1 KB · 缓存于 2026-09-24 22:09:23 · 37.1 KB

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 vault_get by id.

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 Ox0400/dsh-vault 的 README.md。在 GitHub 查看原文 →