Preface¶

In the plugin-based workflow of DeepSeek Harness, evidence is typically generated by different evidence producers. Existing approaches can produce evidence separately, but a small verification layer is still needed: to confirm whether a given subject ID and revision have sufficient, correctly typed, and fixed JSON evidence from independent producers, covering the controls declared in the manifest.

dsh-audit-bundle provides this verification layer. It is not an SBOM scanner, signer, audit logger, policy engine, or archive. Instead, it performs closed verification around an explicit manifest and outputs a content-addressed JSON index.

What This Is¶

dongsheng123132/dsh-audit-bundle is an MIT-licensed DeepSeek Harness plugin for building content-addressed audit indexes across independent DSH evidence producers. It requires Node.js 22 or newer.

One-sentence positioning: given a manifest that declares a subject ID, revision, required controls, fixed JSON evidence, and value-hash assertions, it checks whether the evidence is sufficient and consistent, and generates a verifiable audit index.

Core Capabilities¶

1. Declare Audit Targets with an Explicit Manifest¶

The manifest declares the following:

• A subject ID;
• A revision;
• Required controls;
• Evidence files fixed with SHA-256;
• Bindings from evidence files to subject and revision via JSON Pointers;
• Value-hash assertions.

2. Fail Closed on Verification Failure¶

Verification fails in the following cases:

• Missing, stale, or invalid JSON evidence;
• Subject/revision mismatch;
• Failed assertions;
• Disallowed types;
• Insufficient evidence;
• Insufficient independent producers.

3. Output a Verifiable Index¶

The output includes IDs, types, producers, JSON paths, hashes, statuses, coverage, and a deterministic SHA-256 pair-tree Merkle root.

4. Expose DSH Tools and MCP Service¶

• The DSH bundle registers dsh_audit_bundle_inspect and dsh_audit_bundle_verify. These tools dereference pinned evidence and can write the content-addressed index.
• A companion stdio MCP server registers audit_bundle_inspect and audit_bundle_verify via .mcp.json. It accepts only inline manifests and structural JSONL receipts. The MCP server does not read files, dereference evidence, execute actions, or write artifacts, and reports evidenceContentVerification: not-performed.

Installation and Enablement¶

First, confirm that the runtime environment meets Node.js 22 or newer. The following enables the plugin with audit-bundle as the profile name:

dsh plugin --profile audit-bundle add github:dongsheng123132/dsh-audit-bundle#<commit>

After enabling, view the current profile configuration:

dsh --profile audit-bundle --dump-config

This step is used to confirm that the plugin has appeared in the profile’s configuration.

Typical Usage¶

1. Inspect Only the Manifest and Pinned Evidence¶

The example uses the examples/basic workspace:

node bin/dsh-audit-bundle.mjs inspect --workspace examples/basic --manifest audit.manifest.json

This command checks the pinned JSON evidence declared by the manifest in the specified workspace and outputs a JSON object.

2. Verify and Write a Content-Addressed Index¶

node bin/dsh-audit-bundle.mjs verify --workspace examples/basic --manifest audit.manifest.json --artifactDir artifacts

This command dereferences pinned evidence, writes the content-addressed JSON index under the explicitly specified artifactDir, and then performs read-back verification.

Exit codes are as follows:

• Audit verification failure: 2
• Invalid usage: 1

3. File Boundaries¶

Evidence files must be workspace-relative regular files. The following are rejected:

• Symlinks
• Path escape
• Oversized input
• Excessive structure

Use Cases and Cautions¶

Suitable use case: when you need to prove whether a specific subject/revision has sufficient, correctly typed, and fixed JSON evidence from independent producers, covering controls declared in the manifest.

It is not appropriate to use it as the following tools:

• SBOM scanner
• Signer
• Audit logger
• Policy engine
• Archive

The plugin runs with the current dsh process permissions. Review the source code and license before installation. This plugin is licensed under MIT.

The MCP service only accepts inline manifests and structural JSONL receipts and does not perform actual evidence-content verification. For real evidence-content verification, use the DSH tools or the CLI.

The plugin makes no network calls and starts no child processes; aside from writing the content-addressed JSON index under the explicit artifactDir, it performs no other writes.

Closing Summary¶

The value of dsh-audit-bundle lies in turning “whether evidence is sufficient, consistent, and from allowed independent producers” into a single verifiable closed verification, and outputting a content-addressed index with a Merkle root.

Directory page: DeepSeek Harness Community Directory (URL not provided here; search for dsh-audit-bundle)
GitHub repository: https://github.com/dongsheng123132/dsh-audit-bundle