Preface¶

Under DSH’s “everything is a plugin” philosophy, release verification can also be integrated into the workflow as a tool. A common problem is: after a single build passes, whether the files provided to users from multiple download sources are consistent. The following introduces dsh-release-proof: it downloads all images declared in an explicit release manifest, validates HTTP status, length, SHA-256, and version, and writes content-addressed JSON evidence files.

Positioning¶

dsh-release-proof is positioned as “Reproducible multi-source release evidence for DeepSeek Harness”. In the verified 0.2.0 version, it is a formal Codex plugin and also a standalone stdio MCP server. It provides DSH tools, MCP tools, and CLI commands simultaneously, requiring Node.js 22 or newer, and is licensed under MIT.

Core Features¶

• Downloads all images declared in the explicit release manifest.
• Validates HTTP status, declared length, actual length, SHA-256, and release version.
• Writes content-addressed JSON evidence files.
• Registers DSH tools dsh_release_proof_inspect and dsh_release_proof_verify.
• Exposes a standalone stdio MCP server providing release_manifest_inspect and release_verify.
• Supports CLI inspect and verify commands.

Security Boundaries¶

The verified security constraints are as follows:

• Only anonymous HTTP(S) is allowed; source credentials, custom headers, cookies, query strings, and URL fragments are rejected.
• Each request has manifest-bounded timeout, redirect count, and maximum response size.
• The worker pool limits total concurrent source checks to a range of 1-16.
• The manifest must declare expected version, bytes, and SHA-256; each artifact requires at least two sources.
• The only write target is the explicitly declared workspace-relative artifactDir; traversal and symlink escape are rejected.
• Evidence files are content-addressed, written exclusively, read back, and validated against SHA-256.
• Evidence does not contain timestamps or latency measurements; identical observations produce byte-consistent JSON.
• It does not prove publisher identity, nor does it verify signed release attestations; if the threat model requires these capabilities, it should be paired with signature or provenance verification tools.

Installation and Enablement¶

Requires Node.js 22 or newer. Use the verified installation command:

dsh plugin --profile web add github:dongsheng123132/dsh-release-proof

The package has been verified to have no install lifecycle scripts, and its only runtime dependency is the optional DSH tool SDK peer. The license is MIT. Before installation, it is recommended to review the repository source code and license; when running in DSH, this plugin uses the permissions of the current dsh process.

DSH Tool Usage¶

Version 0.2.0 registers two DSH tools: dsh_release_proof_inspect and dsh_release_proof_verify.

Typical tool parameters are as follows. manifestPath points to the release manifest, and artifactDir specifies the evidence output directory.

{
  "manifestPath": "release/release-manifest.json",
  "artifactDir": "release/evidence"
}

MCP Usage¶

It exposes a standalone stdio MCP server providing two tools:

release_manifest_inspect
release_verify

According to verified information, MCP accepts explicit inline manifestJson, up to 1 MiB in size, and does not read from or write to the file system.

CLI Usage¶

The CLI provides two commands: inspect and verify. Run inspect first, then run verify to perform multi-source checks and write evidence.

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 meanings are as follows:

• 0: All checks passed.
• 2: Valid evidence was written, but the release failed verification.
• 1: Operational error or manifest error.

Local Checks¶

The following verified check commands can be used in the repository:

npm test
npm run check
npm run smoke:plugin
npm run smoke:mcp

Applicable Scenarios and Notes¶

Suitable for:

• Release pipelines that need to confirm multiple download sources return the same version, same length, and same SHA-256.
• Reproducing multi-source release evidence within DSH tools, MCP tools, or CLI.
• Writing evidence files to an explicit artifactDir while preserving content-addressed JSON files.

Notes:

• It validates against expected values given by the manifest, and does not prove publisher identity or signature attestations.
• It only uses anonymous HTTP(S) and cannot carry credentials, custom headers, cookies, query strings, or URL fragments.
• The manifest must declare version, byte count, and SHA-256, and each artifact requires at least two sources.
• The plugin runs with the permissions of the current dsh process; review the source code, MIT license, and dependencies before installation.

Conclusion¶

The value of dsh-release-proof lies in turning multi-source release consistency checks into executable evidence files. GitHub repository address:

https://github.com/dongsheng123132/dsh-release-proof