官方 DSH 内核补丁的数据化版本:10 条自包含补丁 + 自适应应用器(自己找安装位置、逐个备份、语法检查、一键回退),五种打法、零硬编码路径。仅支持 DSH 1.5,后续会跟进更新。 / Official DSH core patches as data: ten patches plus an adaptive applier. Five ways to apply. DSH 1.5 only.
Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
What it doesAI
Official DSH core patches packaged as data: 10 self-contained patches with an adaptive applier that locates installs, backs up, syntax-checks and can roll back.
- 10 self-contained DSH core patches stored as data, no hardcoded paths
- Adaptive applier finds the install, backs up each file and runs syntax checks
- Five apply modes plus one-click rollback; DSH 1.5 only
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Installation
dsh plugin --profile web add github:xiamubumu/dsh-patch-library#v1.0.0Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 |
|---|---|---|
| v1.0.0 | ○ | ○ |
v1.0.0github○ 2 ecosystem plugin2026-10-19
https://github.com/xiamubumu/dsh-patch-library
○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/xiamubumu/dsh-patch-library#v1.0.0
ID: dsh-patch-library@v1.0.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.1-alpha.42026-10-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/xiamubumu/dsh-patch-library#v1.0.0
ID: dsh-patch-library@v1.0.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-patch-library/)`Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static low, dynamic no conclusion — stricter wins → overall low.
v1.0.0v1.0.0git2026-10-21v1.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- warningchildProcess · code-exec
apply.mjs:139const r = spawnSync(process.execPath, ['--check', file], { encoding: 'utf8' }) - warningchildProcess · code-exec
verify.mjs:124const r = spawnSync(process.execPath, [join(LIB_ROOT, 'apply.mjs'), '--check', '--json'], { encoding: 'utf8' })
not in the dynamic queue (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-10-14 · activity: Active
• Repo created: 2026-10-14
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
