DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Config Origin Proof — DSH Plugin for DeepSeek Harness
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
← Plugins
C

dsh-config-origin-proof

Config Origin Proof

Content-addressed evidence for DSH configuration winners and shadowed sources

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:dongsheng123132/dsh-config-origin-proof#84389e3b5ff517286dec32905eb20e01b0c8e46b
READMECompatibilityVersions

Compatibility and provenance

Config Origin Proof is published as dsh-config-origin-proof and currently resolves to version 0.1.1. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
any
Release source
github
Registry updated
9/7/2026

Versions

0.1.1stable
9/7/2026
0.1.0stable
8/21/2026

Related plugins

Loading related plugins…

Latest
0.1.1
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
any
License
MIT
Source
github
GitHub
★ 1
Weekly downloads
0
Last push
9/7/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue

Related plugins

More verified plugins in developer-tools.

Web App@deepseek-ai/dsh-web-appThe dsh browser-surface bundle: the web patch layer over dsh-base plus the runtime glue plugin (frontend dist serving, web-surface prompt, bash runtime variables, URL line)Sdk Minimal@deepseek-ai/dsh-sdk-minimalThe standalone minimal SDK profile bundle: JSON-RPC, one DeepSeek adapter, persistent shell, and JSONL sessionsSdk App@deepseek-ai/dsh-sdk-appThe dsh SDK profile bundle: stdio JSON-RPC serving and process lifecycle over dsh-baseSubagent Codex@deepseek-ai/dsh-subagent-codexOne-shot Codex subagent provider over the official app-server protocol

README

DSH Config Origin Proof

An evidence layer for DeepSeek Harness configuration source ownership. It verifies an explicit redacted recording of precedence domains, source observations, the expected winning source and value digest, shadowed sources, and unobserved higher-priority gaps.

It does not reimplement the DSH composer, collect live configuration, or compare policy changes. DSH's own --dump-config remains the authority for composition. This plugin turns a structured recording from that or another trusted producer into a reproducible receipt. dsh-policy-drift-proof compares baseline and observed policy posture; dsh-profile-lock-proof proves installed bundle closure; this project answers which recorded source won and why.

Raw values and secret-, credential-, prompt-, message- or prose-shaped fields are rejected. Reports contain only stable IDs, SHA-256 digests and verdicts. The verifier fails closed when a higher-priority source is unobserved.

Surfaces

  • DSH: dsh_config_origin_inspect, dsh_config_origin_verify.
  • CLI: dsh-config-origin-proof verify --workspace-root examples --recording recording.json --artifact-dir artifacts.
  • MCP: config_origin_inspect_inline, config_origin_verify_inline; inline-only, no filesystem, network, process or artifact writes.
dsh plugin --profile web add github:dongsheng123132/dsh-config-origin-proof
npm test
npm run check
npm run smoke:plugin
npm run smoke:mcp

The ordering in examples/recording.json follows DSH's published configuration-source ownership contract, but the recording is explicit and revision-bound so a future DSH change cannot silently rewrite old evidence.

MIT