Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
One-click bundle manager that installs and updates 19 DSH plugins: Git server, WebDAV drive, knowledge base, cron tasks, auto-continue, UI tweaks.
- Installs missing bundle members in one click from the settings panel
- Checks npm latest and updates members individually or all at once
- Login gate member adds users, roles, audit log and TOTP 2FA
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 @weibaohui/dsh-fde-toolsInstall 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.6 | ✓ | ✓ | ✓ |
| v0.3.6 | · | · | · |
0.3.6npm✓ 3 runtime-verified2026-10-20
@weibaohui/dsh-fde-tools
✓dsh 0.2.1-rc.2current2026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @weibaohui/dsh-fde-tools@0.3.6
ID: dsh-fde-tools@0.3.6@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
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 · @weibaohui/dsh-fde-tools@0.3.6
ID: dsh-fde-tools@0.3.6@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
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.22026-10-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @weibaohui/dsh-fde-tools@0.3.6
ID: dsh-fde-tools@0.3.6@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.3.6github2026-10-14
https://github.com/weibaohui/dsh-fde-tools
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-fde-tools/)``[](https://www.dsh.so/artifact/dsh-fde-tools/)`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.6dsh manifest0.3.6npm2026-10-210.3.6same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningnetIp · network
client/bundle.js:200st.restart && st.restart.allowed && !loopbackHost() && h('span', { className: 'fde-hint' }, '用 http://127.0.0.1 打开 dsh 才能一键重启'), - warningnetIp · network
client/index.js:190st.restart && st.restart.allowed && !loopbackHost() && h('span', { className: 'fde-hint' }, '用 http://127.0.0.1 打开 dsh 才能一键重启'), - warningshellExec · shell
src/installer.js:298execFile(file, args, { cwd: cwd, timeout: timeout, maxBuffer: 16 * 1024 * 1024, shell: false }, (error, stdout, stderr) => { - warningchildProcess · code-exec
src/restart.js:210' child = spawn(file, args, { cwd, detached, stdio: ["ignore", out, err], env: process.env, shell: viaShell })', - warningchildProcess · code-exec
src/restart.js:239const helper = spawn(nodeExecutable(), ['-e', restartHelperSource(spawned, { cwd: launch.cwd ?? process.cwd() }, { out: logOut, err: logErr - warningfsWrite · files
src/restart.js:186'const note = (line) => { try { fs.appendFileSync(logErr, `[dsh-fde-tools] ${line}\\n`) } catch {} }',
show 2 audit findings
- mediumensureAllowBuilds silently rewrites pnpm 'set this to true or false' placeholders to true in the profile workspace
src/installer.js:563Reachable from POST /install or /update: when pnpmAdd fails with 'Ignored build scripts', ensureAllowBuilds rewrites the profile's pnpm-workspace.yaml. It does not only enable the packages reported in that output; it also flips every pre-existing 'set this to true or false' placeholder and every legacy list-form entry to `true`. As a result, postinstall (lifecycle script) code from npm packages runs on the host without an explicit per-package decision, and the permission persists in the profile for later installs.
- mediuminstall/update endpoint has weaker trust checks than restart and fail-opens to 'install all pack members' on a bad body
src/index.js:78These state-changing routes are gated only by ctx.connection.requestRejection (line 54), unlike /restart which also enforces loopback + Origin===Host (line 93), and readJsonBody never checks the content type. Any request that clears the framework fence but carries a malformed or absent body yields names=null, which installer.install resolves to the whole PACK: 19 third-party packages installed (with lifecycle scripts), plus writes to the profile package.json, pnpm-workspace.yaml and a snapshot file. The blast radius depends on how strict the host's requestRejection actually is.
No critical/high issues: package specs are allow-listed and execFile uses shell:false, but two medium gaps remain in the install path (fail-open body handling, silent allowBuilds escalation).
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-09 · activity: Active
• Repo created: 2026-09-12
• Stars: ★ 2 · 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).