iiwish/dsh-testkit

Name: iiwish/dsh-testkit
Author: iiwish

Plugin插件 Native原生 ⭐ 2 MIT Dev Workflow开发与代码工作流 Docs & Writing文档与写作

DeepSeek Harness 插件的生命周期一致性测试

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

dsh-testkit is a purpose-built release gate tool for DeepSeek Harness plugin maintainers, designed to catch issues that may slip past unit tests and static checks. To install it, you add it as a dev dependency to your plugin project with pnpm add -D dsh-testkit, then initialize the test configuration with pnpm dsh-test init. It runs the full lifecycle of your plugin on an isolated, real DSH host, covering installation, registration, functional checks, uninstallation, and post-uninstall cleanup. It does not make any LLM API calls, so you do not need an API key to use it.

This tool is intended for plugin maintainers, release PR reviewers, plugin template maintainers, and developers that need reproducible host-level bug reports for DSH. It is designed to run as a pre-release quality gate, not as a replacement for unit test frameworks, static linters, or security certifications. Most users integrate it into their CI pipeline to run on release pull requests and version tags, after running cheaper static checks on every commit. You can also run it locally on your development machine before pushing a release, to verify your plugin works correctly before publishing. It exercises one plugin per isolated run, so multi-plugin composition issues are handled outside of its scope.

dsh-testkit requires Node.js 22 or newer and Docker to run, and it is released under the open source MIT license. Docker is the default runner, and it uses Docker to isolate test runs, limit resource usage, and drop unnecessary capabilities to reduce the blast radius of untrusted plugins. While Docker improves safety, dsh-testkit is not a hardened malware sandbox, so you should always use disposable infrastructure when testing untrusted plugins. It has no SaaS dependency and does not upload any data unless you configure your CI workflow to do so. Test results are saved locally as JSON, JUnit XML, and human-readable markdown reports for your review.

dsh-testkit 是专为 DeepSeek Harness（DSH）插件开发者设计的发布前测试工具，用于在真实 DSH 宿主环境中验证待发布插件包的安装、注册、运行和卸载全流程。它测试用户实际会安装的构件，而非仅针对源码运行单元测试，能提前发现文件缺失、宿主注册失败、卸载残留等常见发布问题，为开发者留存可审查的完整测试证据，且它不调用大模型，也不需要配置模型 API 密钥。

该工具适合维护 DSH 插件、审核发布 PR、使用插件模板开发新插件，或是需要生成可复现宿主级问题报告的开发者使用。它可以轻松集成到 GitHub CI 流水线中，默认推荐在版本发布 PR 和打标签时运行，每次测试在隔离环境中仅验证一个目标插件，自动完成从解析依赖到清理环境的完整生命周期测试流程。

dsh-testkit 需要 Node.js 22 或更高版本，以及 Docker 环境，默认使用 Docker 作为运行器来降低测试对本地环境的影响，遵循 MIT 许可完全开源发布。使用 Docker 可以缩小不受信任插件的攻击范围，但它并非经过加固的恶意软件沙箱，测试未知或不受信任的插件时，建议使用一次性隔离基础设施运行测试。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-testkit（iiwish/dsh-testkit）
仓库：https://github.com/iiwish/dsh-testkit
本站详情页：https://www.yhbd.top/plugins/iiwish-dsh-testkit/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 2 · 最近提交 2026-09-26 · 主语言 TypeScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意

Only 2 stars - very few users, little community feedback星标只有 2，几乎没人在用，遇到问题缺少社区反馈

DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装

dsh plugin --profile web add dsh-testkit@0.4.4

把 iiwish/dsh-testkit 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

10.7 KB · 缓存于 2026-09-10 19:42:30 · 10.7 KB

DSH Testkit

The real-host release gate for DeepSeek Harness plugins.

简体中文 · Scenario reference · Architecture · Contributing

A plugin can compile, pass unit tests, and still fail after publication because files are missing from the tarball, its bundle does not register in DSH, or uninstall leaves the profile broken. DSH Testkit closes that gap: it tests the artifact a user actually installs against an exact, real DSH host and retains evidence a maintainer can review.

It makes no model call and needs no model API key.

At A Glance

Release question	Evidence from one isolated run
Does the publishable artifact install and register?	`npm pack`, exact DSH installation, bundle assembly, config rows, services, and tool schemas
Does its promised behavior work?	Deterministic runtime probes, declared tool calls, optional loopback HTTP routes, and explicit browser smoke
Can a user remove it cleanly?	Uninstall, same-profile reboot, capability checks, owned-path residue, processes, and ports

Use DSH Testkit when you maintain a DSH plugin, review a release PR, operate a plugin template, or need a reproducible host-level bug report. It is intentionally a release gate, not another unit-test framework, static linter, model-output evaluator, or security certification.

Quick Start

Requirements: Node.js 22 or newer and Docker.

pnpm add -D dsh-testkit
pnpm dsh-test init
pnpm dsh-test

For a bundle below the repository root:

pnpm dsh-test init plugin/
pnpm dsh-test --config plugin/dsh-testkit.yaml

dsh-test init works offline, finds the nearest Git worktree, and creates three reviewable files:

<plugin-root>/dsh-testkit.yaml with the exact DSH version and detected row expectations
<repository-root>/.github/workflows/dsh-lifecycle.yml with a read-only default token contract and correct nested paths
<repository-root>/.agents/skills/dsh-testkit/SKILL.md so compatible coding agents apply the same gate

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 iiwish/dsh-testkit 的 README.md。在 GitHub 查看原文 →