DeepSeek Harness 插件

dsh-profile-lock-proof

Content-addressed proof that a DeepSeek Harness profile declaration, pnpm lock and installed bundles agree(英文原文)

跳到安装方式

来源信息

GitHub 仓库
dongsheng123132/dsh-profile-lock-proof
最近更新
2026年8月20日
分类
插件开发工具
GitHub stars
2
载体类型
plugin
目录证据
上游声明已找到 dsh.bundle
证据路径
package.json#dsh.bundle
核对版本
0.1.0-rc.8
上游核对日期
2026-08-20

该证据由上游目录提供。本站没有安装、运行或安全审核这个插件。

安装

默认先复制一段 Prompt,让 Agent 读 GitHub 仓库和源码;需要自己装时再切到命令。

复制这段 Prompt,发给 DSH、Codex 或其他 Agent,让它先读 GitHub 仓库和源码。

请先不要安装或执行任何命令。阅读这个插件的 GitHub 仓库、README 和关键源码,然后用清楚、直接的方式回答以下问题,帮助我判断它是否适合我的需求:

1. 这个插件是什么,解决什么问题;
2. 适合哪些用户和典型使用场景;
3. 安装后如何使用,并给出一个最小使用示例;
4. 有哪些已知限制,以及隐私、安全、兼容性或维护风险;
5. 给出“推荐 / 有条件推荐 / 不推荐”的明确建议和理由。

请区分仓库明确说明、根据源码推断和未知信息。证据不足时请明确说明,不要猜测或照抄 README。

GitHub:https://github.com/dongsheng123132/dsh-profile-lock-proof
插件名:dsh-profile-lock-proof
作者:dongsheng123132

检查来源文件

安装前先看这个插件目录里的 README 和其他文件。

文件资源管理器3 个文件
README.md来源说明 · 只读预览

dsh-profile-lock-proof

![CI](https://github.com/dongsheng123132/dsh-profile-lock-proof/actions/workflows/ci.yml) ![MIT license](LICENSE) ![Node.js 22+](package.json) ![Awesome DSH Plugins](https://github.com/dongsheng123132/awesome-dsh-plugins#2origin-plugin-lab)

dsh-profile-lock-proof produces a content-addressed, machine-readable proof that a DeepSeek Harness profile's dependency declaration, pnpm lock importer, installed package manifests, and each package's declared dsh.bundle.patch agree.

It is deliberately narrower than an SBOM, CVE scanner, signature verifier, or installer. It does not execute packages, contact the network, mutate a profile, or return manifest, lockfile, patch, script-command, or secret contents.

Version 0.2.0 removes the bundled DSH tool runtime and the default export that stock Cordis Loader misclassified. The bundle now exposes host-neutral tool definitions through its namespace export; local-path and fixed-commit installs are exercised against the real stock Web profile.

Proof boundary

  • Input paths are workspace-relative regular files; traversal and symlinks are rejected.
  • Profile and lockfile bytes must match the SHA-256 values in an explicit proof manifest.
  • Dependency specifiers must be exact semver or github:owner/repo#<40-hex-commit>.
  • The pnpm importer specifier, installed name/version/package hash, bundle patch path/hash, and absence of lifecycle hooks must all agree.
  • Missing, stale, invalid, mutable, mismatched, or lifecycle-script-bearing evidence fails closed.
  • Output contains identities, classifications, hashes, status, and disclosure only. Reports are written atomically under an explicit artifactDir and read back.

CLI

dsh-profile-lock-proof inspect --workspace . --manifest proof.json
dsh-profile-lock-proof verify --workspace . --manifest proof.json --artifactDir artifacts

Exit 0 means a verified proof, 2 means verification or input failure.

DSH / MCP tools

  • dsh_profile_lock_inspect
  • dsh_profile_lock_verify
  • MCP aliases: profile_lock_inspect, profile_lock_verify

The MCP surface is deliberately lower privilege: it accepts bounded inline evidence only, never reads or writes files, and shares the validation core. DSH/CLI may write only to an explicit workspace-relative artifactDir, atomically and with read-back verification.

Install into an isolated profile:

dsh plugin --profile profile-lock add github:dongsheng123132/dsh-profile-lock-proof#<commit>

Development

npm ci
npm test
npm run check
npm run smoke:plugin
npm run smoke:mcp
npm run smoke:web-loader # requires DSH_CHECKOUT and isolated DSH_HOME

MIT licensed. See [SECURITY.md](SECURITY.md) for the threat boundary.