Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
DSH plugin that turns an empty folder into a test-framework skeleton and injects testing constraints into AI sessions.
- Scaffolds a test-framework skeleton from an empty folder
- Splits requirement docs into modules and confirms versions
- Registers test environments, accounts and cross-document links in AI sessions
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 dsh-test-frameworkInstall method: npm · runtime verified (L5)
Verification & Compatibility
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 | dsh 0.2.1-alpha.2 |
|---|---|---|---|
| 0.3.1 | · | · | · |
| 0.3.0 | ✓ | ✓ | · |
| 0.2.8 | · | · | ✓ |
0.3.1npm2026-10-21
dsh-test-framework
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.3.0npm✓ 2 runtime-verified2026-10-20
dsh-test-framework
✓dsh 0.2.1-rc.2current2026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-test-framework@0.3.0
ID: dsh-test-framework@0.3.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
↳ carried from earlier record dsh-test-framework@0.3.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-test-framework@0.3.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-test-framework@0.3.1@dsh0.2.1-rc.2 (l3-fullscan)
active in loader tree (150 entries)
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-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-test-framework@0.3.0
ID: dsh-test-framework@0.3.0@dsh0.2.1-alpha.4 · profile: l3-fullscan
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-test-framework@0.3.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-test-framework@0.3.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-test-framework@0.3.1@dsh0.2.1-rc.2 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.2.8npm✓ 1 runtime-verified2026-10-15
dsh-test-framework
✓dsh 0.2.1-alpha.22026-10-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-test-framework@0.2.8
ID: dsh-test-framework@0.2.8@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
↳ carried from earlier record dsh-test-framework@0.3.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-test-framework@0.3.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-test-framework@0.3.1@dsh0.2.1-rc.2 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-test-framework/)``[](https://www.dsh.so/artifact/dsh-test-framework/)`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 medium — stricter wins → overall medium.
v0.3.1dsh manifest0.3.1npm2026-10-210.3.1same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (10)
- warningchildProcess · code-exec
lib/framework.js:1394const probe = spawnSync('git', ['--version'], { encoding: 'utf8', timeout: 8000, windowsHide: true }) - warningchildProcess · code-exec
lib/framework.js:1396const run = spawnSync('git', ['init', '--quiet'], { cwd, encoding: 'utf8', timeout: 20000, windowsHide: true }) - warningfsWrite · files
lib/framework.js:163fs.writeFileSync(file, content, 'utf8') - warningfsWrite · files
lib/framework.js:336fs.writeFileSync(tmp, `${JSON.stringify(next, null, 2)}\n`, 'utf8') - warningfsWrite · files
lib/framework.js:1363fs.writeFileSync(path.join(gitPath, 'HEAD'), 'ref: refs/heads/main\n', 'utf8') - warningchildProcess · code-exec
lib/install.js:44const r = spawnSync(command, args, { encoding: 'utf8', ...base }) - warningchildProcess · code-exec
lib/install.js:52const r2 = spawnSync(command, args, { ...base, stdio: quietFallback ? 'ignore' : 'inherit' }) - warningfsWrite · files
lib/install.js:376fs.writeFileSync(backup, raw, 'utf8') - warningfsWrite · files
lib/install.js:385fs.writeFileSync(manifestPath, `${JSON.stringify(manifest, null, 2)}\n`, 'utf8') - warningfsWrite · files
lib/install.js:460fs.writeFileSync(backup, raw, 'utf8')
show 3 audit findings
- mediumWorkspace-controlled names are injected into the DSH system prompt with no sanitisation
lib/index.js:215The prompt-gate text produced by renderGate/frameworkStatus is assembled from workspace-controlled strings: product directory names (`- 产品「${p.name}」缺 …`) and asks built from registry fields such as `modules[].name`, `relations[].from/to`, `docs[].name` and end names (`这些模块声明了非默认端或有关联边…：${involved.join('、')}`). Only `{{` is escaped, so a crafted workspace whose `_框架配置/框架登记.json` (or directory names) contain instruction-like text has that text delivered to the model as part of the system prompt, letting repository content steer the agent beyond the plugin's intent.
- lowEnvironment and DB passwords are written in plaintext into workspace markdown
lib/framework.jsrecordEnvironments persists plaintext page/DB credentials into `<产品>\_框架配置\环境与账密.md` (and into appended fallback tables). That file lives in the user's framework folder, which is typically version-controlled, archived or copied along with reports; credentials therefore leak beyond the machine that was intended to hold them. The JSON registry keeps only a `passwordStored` pointer, so the md file is the leak surface.
- lowinstall/uninstall CLI rewrites the DSH profile outside the workspace and can spawn pnpm via a shell
lib/install.js:38applyInstall/applyUninstall edit `<dshHome>\profiles\<name>\package.json` (dependencies + dsh.profile.bundles), delete/create a junction under the profile's node_modules, and can additionally run `dsh plugin add link:…` or `pnpm install` (which rewrites node_modules and needs network). The runCapture shell fallback, combined with a user-supplied `--dsh` path ending in .cmd/.bat, means shell metacharacters in that argument are interpreted by cmd.exe. Everything requires a deliberate --apply/--official/--pnpm invocation and package.json is backed up first, so impact is limited to the invoking us
Static warnings come from gated scaffolding/install code; residual risk is workspace-controlled names reaching the system prompt unsanitised, plus plaintext env passwords.
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-19 · 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).