dongsheng123132/dsh-release-proof

Name: dongsheng123132/dsh-release-proof
Author: dongsheng123132

Plugin插件 Native原生 ⭐ 2 MIT Dev Workflow开发与代码工作流 Approval & Security审批与安全

DeepSeek Harness 工件及其镜像的可复现多源发布证据

Project Overview项目介绍

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

This is a native DeepSeek Harness plugin for reproducible release artifact verification across multiple download mirrors. It can be installed directly into DSH via the command dsh plugin --profile web add github:dongsheng123132/dsh-release-proof, which fetches the standard DSH bundle declared in the package.json. The DSH native plugin registers two commands: dsh_release_proof_inspect to summarize the manifest without exposing URLs, and dsh_release_proof_verify to run full checks. It also supports three usage modes: DSH native plugin command, standalone CLI, and standalone stdio MCP server, each with dedicated entry points for different workflows.

The typical workflow starts with a pre-defined release manifest that lists all artifact sources, expected version, byte length, and SHA-256 hash for each release artifact. The tool downloads every artifact mirror declared in the manifest, checks HTTP status codes, compares the advertised values to actual downloaded values, then outputs a deterministic content-addressed JSON evidence file if all checks pass. The exit code for standalone CLI use is 0 for all checks passed, 2 for valid proof written but failed verification, and 1 for operational or manifest errors.

The tool follows a strict safety model that blocks any authenticated requests, custom headers, cookies, and path traversal or symlink escape attacks. It enforces bounded timeouts, redirect counts, maximum response sizes, and caps total concurrent checks between 1 to 16 workers. It requires at least two sources per artifact, runs on Node.js 22 or newer, is released under the permissive MIT license, and has no runtime dependencies outside of the optional DSH SDK.

这是一款专为DeepSeek Harness开发的原生插件，用于提供可复现的多源发布产物校验。它可以通过DSH的Web插件管理器一键安装，同时也支持作为独立CLI工具和MCP服务器运行，针对不同使用场景暴露了对应的命令接口，核心功能是验证不同下载镜像站点的发布产物一致性。

工具的典型工作流是读取开发者提供的发布清单文件，下载清单中声明的所有镜像产物，逐一校验HTTP状态、文件大小、SHA-256哈希和版本号，校验完成后生成内容寻址的JSON证据文件，填补了CI通过到用户收到一致发布包之间的信任缺口。

本工具遵循严格的安全模型，仅允许匿名HTTP请求，限制了并发数、超时、重定向次数和响应大小，要求每个产物至少有两个源，禁止路径遍历和符号链接逃逸，项目基于MIT许可证开源，需要Node.js 22或更高版本运行。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

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

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

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

【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 warning1 项注意

Only 2 stars - very few users, little community feedback星标只有 2，几乎没人在用，遇到问题缺少社区反馈

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 github:dongsheng123132/dsh-release-proof

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

READMEREADME

4.3 KB · 缓存于 2026-08-23 03:42:15 · 4.3 KB

dsh-release-proof

Reproducible multi-source release evidence for DeepSeek Harness.

dsh-release-proof downloads every mirror declared in an explicit release manifest, verifies HTTP status, advertised and actual byte length, SHA-256, and release version, then writes a content-addressed JSON evidence file. It is aimed at the gap between “CI passed” and “users are receiving the same release from every download endpoint.”

Version 0.2.0 is a formal Codex plugin and standalone MCP server, and uses the namespace export shape required by the stock DSH Web Loader. A real Cordis boot regression test guards that loader contract.

This tool proves transport and mirror consistency against values supplied by the manifest. It does not prove publisher identity or verify signed release attestations; use a signature/provenance verifier alongside it when that is part of your threat model.

Safety model

Anonymous HTTP(S) only: source credentials, custom headers, cookies, query strings, and URL fragments are rejected.
Every request has a manifest-bounded timeout, redirect count, and maximum response size.
A worker pool caps total concurrent source checks (1–16).
The manifest must declare the expected version, bytes, and SHA-256; each artifact needs at least two sources.
The only write target is the explicit, workspace-relative artifactDir. Traversal and symlink escape are rejected.
Evidence is content addressed, written exclusively, read back, and SHA-256 verified.
Evidence contains no timestamps or latency measurements, so identical observations produce byte-identical JSON.

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

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