deepseekplugins

DeepSeek Harness plugin

dsh-profile-lock-proof

Content-addressed proof that a DeepSeek Harness profile declaration, pnpm lock and installed bundles agree

Development & Runtime
Jump to install

Source facts

Repository
dongsheng123132/dsh-profile-lock-proof
Latest update
Aug 20, 2026
Category
Development & Runtime
GitHub stars
2
Format
plugin
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/dongsheng123132/dsh-profile-lock-proof
Plugin: dsh-profile-lock-proof
Author: dongsheng123132

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer3 files
README.mdSource · read only

dsh-profile-lock-proof

![CI](https://github.com/dongsheng123132/dsh-profile-lock-proof/actions/workflows/ci.yml) ![MIT license](LICENSE) ![Node.js 22+](package.json) ![Awesome DSH Plugins](https://github.com/dongsheng123132/awesome-dsh-plugins#2origin-plugin-lab)

dsh-profile-lock-proof produces a content-addressed, machine-readable proof that a DeepSeek Harness profile's dependency declaration, pnpm lock importer, installed package manifests, and each package's declared dsh.bundle.patch agree.

It is deliberately narrower than an SBOM, CVE scanner, signature verifier, or installer. It does not execute packages, contact the network, mutate a profile, or return manifest, lockfile, patch, script-command, or secret contents.

Version 0.2.0 removes the bundled DSH tool runtime and the default export that stock Cordis Loader misclassified. The bundle now exposes host-neutral tool definitions through its namespace export; local-path and fixed-commit installs are exercised against the real stock Web profile.

Proof boundary

  • Input paths are workspace-relative regular files; traversal and symlinks are rejected.
  • Profile and lockfile bytes must match the SHA-256 values in an explicit proof manifest.
  • Dependency specifiers must be exact semver or github:owner/repo#<40-hex-commit>.
  • The pnpm importer specifier, installed name/version/package hash, bundle patch path/hash, and absence of lifecycle hooks must all agree.
  • Missing, stale, invalid, mutable, mismatched, or lifecycle-script-bearing evidence fails closed.
  • Output contains identities, classifications, hashes, status, and disclosure only. Reports are written atomically under an explicit artifactDir and read back.

CLI

dsh-profile-lock-proof inspect --workspace . --manifest proof.json
dsh-profile-lock-proof verify --workspace . --manifest proof.json --artifactDir artifacts

Exit 0 means a verified proof, 2 means verification or input failure.

DSH / MCP tools

  • dsh_profile_lock_inspect
  • dsh_profile_lock_verify
  • MCP aliases: profile_lock_inspect, profile_lock_verify

The MCP surface is deliberately lower privilege: it accepts bounded inline evidence only, never reads or writes files, and shares the validation core. DSH/CLI may write only to an explicit workspace-relative artifactDir, atomically and with read-back verification.

Install into an isolated profile:

dsh plugin --profile profile-lock add github:dongsheng123132/dsh-profile-lock-proof#<commit>

Development

npm ci
npm test
npm run check
npm run smoke:plugin
npm run smoke:mcp
npm run smoke:web-loader # requires DSH_CHECKOUT and isolated DSH_HOME

MIT licensed. See [SECURITY.md](SECURITY.md) for the threat boundary.

Back to searchOpen GitHub repository

More related plugins

View category