deepseekplugins

DeepSeek Harness plugin

dsh-windows-readiness-proof

Content-addressed readiness proof for sanitized DeepSeek Harness observations on managed Windows hosts

Development & Runtime
Jump to install

Source facts

Repository
dongsheng123132/dsh-windows-readiness-proof
Latest update
Aug 14, 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-windows-readiness-proof
Plugin: dsh-windows-readiness-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-windows-readiness-proof

![CI](https://github.com/dongsheng123132/dsh-windows-readiness-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-windows-readiness-proof evaluates a SHA-256-pinned, sanitized observation of a managed Windows host against explicit DeepSeek Harness readiness requirements.

It is an evidence verifier, not a collector or remediation tool. It never runs PowerShell, reads the registry, changes Group Policy, creates Defender exclusions, edits WDAC/AppLocker, installs software, restarts services, or probes the network.

What it proves

An explicit manifest fixes an opaque machine digest, snapshot revision, observation bytes, evaluation time, maximum evidence age, and requirements for:

  • Windows product type, architecture, build, and pending reboot;
  • Node, DSH, PowerShell edition/version, and language mode;
  • classified WDAC, AppLocker, Defender, execution policy, Credential Guard, and TLS 1.2 posture;
  • long paths, atomic rename, workspace/temp ACL class, and symlink policy;
  • non-interactive session, opaque identity class, writable profile, and recovery configuration;
  • free workspace/temp storage;
  • required connectivity identities represented only by endpoint SHA-256 plus status/TLS/proxy classes.

Missing, stale, future, malformed, secret-shaped, identity-bearing, path-escaping, symlinked, or policy-mismatched evidence fails closed. Reports expose only opaque identities, hashes, classifications, reason codes, and control status—not usernames, domains, endpoints, registry paths, command output, credentials, or raw observations.

Complementary boundary

Harness Doctor diagnoses local DSH/Codex/OpenClaw installation health. Windows desktop-control skills execute UI and PowerShell actions. This plugin does neither: it verifies a pre-collected enterprise readiness fact set under a reviewable policy and produces a deterministic artifact suitable for CI or audit.

CLI

dsh-windows-readiness-proof inspect --workspace . --manifest manifest.json
dsh-windows-readiness-proof verify --workspace . --manifest manifest.json --artifactDir artifacts

Exit 0 means verified; exit 2 means a readiness or evidence failure.

DSH / MCP tools

The DSH entry is a namespace plugin (name / inject / apply) with no default export. This is part of the shipped compatibility contract: the real Cordis Loader must retain the tools injection when a stock Web profile loads the bundle. The plugin smoke and structural check fail if a default export is reintroduced.

For a built DSH checkout and an isolated Web profile containing this bundle, run DSH_CHECKOUT=/path/to/dsh DSH_HOME=/path/to/isolated-home npm run smoke:web-loader. The smoke starts the real stock Web profile with a bounded, credential-free environment and requires an actual readiness URL.

  • dsh_windows_readiness_inspect
  • dsh_windows_readiness_verify
  • MCP aliases: windows_readiness_inspect, windows_readiness_verify
dsh plugin --profile windows-readiness add github:dongsheng123132/dsh-windows-readiness-proof#<commit>

See [examples/README.md](examples/README.md) for a synthetic, non-collecting example. MIT licensed.

Back to searchOpen GitHub repository

More related plugins

View category