Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
Installation
dsh plugin --profile web add github:a1141171521/dsh-plugin-memfuseInstall method: GitHub · 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 |
|---|---|
| 5b8848 | ✓ |
5b8848github✓ 1 runtime-verified2026-10-19
https://github.com/a1141171521/dsh-plugin-memfuse
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/a1141171521/dsh-plugin-memfuse (version unstated)
ID: dsh-plugin-memfuse@5b8848@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-plugin-memfuse/)``[](https://www.dsh.so/artifact/dsh-plugin-memfuse/)`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.1.0dsh manifest0.1.0git2026-10-210.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalshellExec · shell
lib/update.js:40exec( - warningchildProcess · code-exec
docs/preview/serve.mjs:63spawn(opener[0], opener[1], { stdio: 'ignore', detached: true }).unref(); - warningnetIp · network
docs/preview/serve.mjs:32const url = new URL(req.url ?? '/', 'http://127.0.0.1'); - warningnetIp · network
docs/preview/serve.mjs:55const url = `http://127.0.0.1:${PORT}${PAGE}`;
show 1 audit findings
- mediumDev preview server serves any repo file over loopback HTTP without Host validation
docs/preview/serve.mjs:34If a developer runs `npm run preview`, any file under the repo root is served, including `.git/config` (which may embed a remote URL with a token) and any committed/generated secrets. The `startsWith(ROOT)` check only confines the path; it does not restrict which repo files are exposed and there is no Host-header validation, so a malicious web page can use DNS rebinding to reach 127.0.0.1:PORT as same-origin and read those files.
Only concrete issue is the dev preview HTTP server exposing any repo file on loopback without Host validation (DNS-rebinding exfil); runtime entry lib/index.js not provided.
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-18 · activity: Active
• Repo created: 2026-10-14
• Stars: ★ 3 · 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).
