dsh-release-proof
DeepSeek Harness 的可复现多源发布证据
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:dongsheng123132/dsh-release-proof#1c6ef06c0b6a3ca0fa289bbf76699a710d8d25f4Release Proof 以 dsh-release-proof 发布，当前版本为 0.2.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
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.
artifactDir. Traversal and symlink escape are rejected.dsh plugin --profile web add github:dongsheng123132/dsh-release-proof
The package exposes a standard DSH bundle through package.json#dsh.bundle.patch and registers:
dsh_release_proof_inspect — safely summarize a manifest without returning URLs.dsh_release_proof_verify — verify all sources and write a proof artifact.Typical tool arguments:
{
"manifestPath": "release/release-manifest.json",
"artifactDir": "release/evidence"
}
The plugin also exposes a standalone stdio MCP server through .mcp.json:
release_manifest_inspectrelease_verifyMCP accepts an explicit inline manifestJson of at most 1 MiB. It does not read or write the filesystem. Verification still uses anonymous HTTP(S), the manifest's timeout/concurrency/redirect/byte limits, and returns a deterministic content-address descriptor that can be recomputed by the caller.
dsh-release-proof inspect \
--root /path/to/workspace \
--manifest release/release-manifest.json
dsh-release-proof verify \
--root /path/to/workspace \
--manifest release/release-manifest.json \
--artifact-dir release/evidence
Exit code 0 means every check passed, 2 means a valid proof was written but the release failed verification, and 1 means an operational or manifest error.
See examples/release-manifest.example.json. A source can obtain the version from an artifact response header:
{ "kind": "header", "name": "x-release-version" }
or an anonymous JSON sidecar:
{ "kind": "json", "url": "https://downloads.example.com/version.json", "field": "release.version" }
field is a dot-separated object path. Redirect targets receive the same anonymous-URL validation before they are requested.
npm test
npm run check
npm run smoke:plugin
npm run smoke:mcp
python C:/Users/ZhuanZ/.codex/skills/.system/plugin-creator/scripts/validate_plugin.py .
Requires Node.js 22 or newer. The package has no install lifecycle scripts and no runtime dependencies beyond the optional DSH tool SDK peer.
MIT