dongsheng123132/dsh-audit-bundle
跨独立DeepSeek Harness证据生产者的内容寻址审计索引
Project Overview项目介绍
This is a native DSH plugin built exclusively for DeepSeek Harness, focused on creating content-addressed audit indexes for evidence from independent DSH evidence producers. It provides two DSH-native tools, and also exposes a command-line interface for local inspection and verification runs, alongside a Codex MCP interface for proof-only verification. You can install it directly via the DSH CLI by running dsh plugin --profile audit-bundle add github:dongsheng123132/dsh-audit-bundle#<commit>, replacing the commit placeholder with your target desired version. It requires Node.js 22 or newer to run, it is distributed under the open MIT license, and it hosts continuous integration tests on both Ubuntu and Windows platforms.
It fills a missing verification layer in the DSH ecosystem, as existing tools already handle dependency scanning, SBOM generation, signing, audit logging, and policy enforcement. This plugin does not bundle a second DSH runtime, and only handles the core task of verifying that a particular subject and revision has enough pinned evidence from allowed independent producers to cover all declared controls. Users define all verification requirements in an explicit manifest that lists the subject ID, revision, required controls, evidence constraints, allowed producers, and SHA-256 pinned evidence files for the audit run.
The plugin fails closed on any verification issue, returning a failed verdict for missing, stale, or invalid evidence, subject and revision mismatches, failed assertions, disallowed evidence types, and insufficient evidence or independent producers. It outputs all verification results as structured JSON, including entry IDs, evidence types, producer information, JSON pointers, hashes, statuses, coverage metrics, and a deterministic SHA-256 pair-tree Merkle root. It never copies full evidence bodies or assertion values, rejects non-standard inputs like symlinks, oversized files, path escapes, and overly complex structures, and performs no network calls or child process spawns.
这是一个专为DeepSeek Harness(DSH)打造的原生审计bundle插件,用于为来自不同独立DSH证据生成器的证据生成内容寻址的审计索引。它提供了两个DSH原生工具,同时暴露了Codex MCP接口用于仅证明验证,还附带了命令行接口支持本地检查和验证操作。该项目遵循MIT许可协议,运行要求Node.js 22及以上版本,可通过DSH插件命令直接从仓库添加安装。
这个插件填补了现有DSH生态中审计验证层的空白,它不会重复实现SBOM扫描、签名、审计日志或策略引擎这类已有工具的功能,只专注于验证特定主题/修订版本是否满足来自允许独立生产者的足够证据,覆盖声明的控制要求。用户可通过明确的清单声明主题ID、修订版本、所需控制项、证据要求、哈希锚定的证据文件等验证规则。
验证失败时会直接关闭输出,对于缺失、过期或无效证据,主题/修订不匹配,断言失败等问题都会返回失败结果。输出包含ID、类型、生产者、JSON路径、哈希、状态、覆盖率和确定的默克尔根,不会复制证据主体或断言值。仅接受工作区相对的常规文件,拒绝符号链接、路径逃逸、过大输入和过度结构,不执行网络调用或子进程。
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】,检查通过再动手。
插件:dsh-audit-bundle(dongsheng123132/dsh-audit-bundle)
仓库:https://github.com/dongsheng123132/dsh-audit-bundle
本站详情页:https://www.yhbd.top/plugins/dongsheng123132-dsh-audit-bundle/
本站登记:类型 bundle · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 2 · 最近提交 2026-09-07 · 主语言 JavaScript
按下面顺序执行,每步先把结论告诉我,再进入下一步:
【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 更稳。
- 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 github:dongsheng123132/dsh-audit-bundle
把 dongsheng123132/dsh-audit-bundle 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
dsh-audit-bundle
Content-addressed audit indexes across independent DeepSeek Harness evidence producers.
Version 0.2 adds a formal proof-only Codex MCP surface, host-neutral DSH ToolDefinitions, real ToolRuntime calls and a stock Web Loader regression test. The package exposes namespace exports only and does not bundle a second DSH runtime.
This plugin is not an SBOM scanner, signer, audit logger, policy engine or archive. Existing tools already scan dependencies and individual 2Origin plugins already produce release, runtime, recovery, lineage and policy evidence. The missing layer is a small verifier that proves a particular subject/revision has enough pinned evidence from allowed, independent producers to cover declared controls.
Contract
An explicit manifest declares:
- one subject ID and revision;
- required controls with minimum eligible evidence, minimum distinct producers and allowed evidence types;
- evidence files pinned by SHA-256;
- JSON Pointers that bind every evidence file to the subject and revision;
- value-hash assertions, so expected or observed values never enter the audit index.
Verification fails closed for missing, stale or invalid JSON evidence, subject/revision mismatch, failed assertions, disallowed types, insufficient evidence or insufficient independent producers. The output contains IDs, types, producers, paths into JSON, hashes, statuses, coverage and a deterministic SHA-256 pair-tree Merkle root. It never copies evidence bodies or assertion values.
Files must be workspace-relative regular files. Symlinks, path escape, oversized input and excessive structure are rejected. The plugin performs no network calls or child processes and writes only a content-addressed JSON index under the explicit artifactDir, followed by read-back verification.
Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要,完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →
Minglink/dsh-infinite-gen-4
kenryu42/cc-safety-net
hyhmrright/brooks-lint
toby-bridges/api-relay-audit
hashgraph-online/hol-guard
SeaOf0/dsh-redteam-model
howmp/dsh-pentest
saya-ch/dsh-mobile