Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
What it does
Installation
dsh plugin --profile web add github:LLL-lyh0/dsh-accelerator#v0.1.0Install 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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.1-rc.3 current |
|---|---|
| v0.1.0 | ✓ |
v0.1.0github✓ 1 runtime-verified2026-10-28
https://github.com/LLL-lyh0/dsh-accelerator
✓dsh 0.2.1-rc.3current2026-10-28L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/LLL-lyh0/dsh-accelerator#v0.1.0
ID: dsh-accelerator@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
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-accelerator/)``[](https://www.dsh.so/artifact/dsh-accelerator/)`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 high; dynamic no conclusion (static stands) → overall high.
v0.1.0dsh manifestv0.1.0git2026-10-28v0.1.0same versionsuspicious · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningshellExec · shell
lib/ca-install.mjs:17execFile(CERTUTIL, args, { windowsHide: true, maxBuffer: 8 << 20 }, (err, stdout, stderr) => { - warningshellExec · shell
lib/ca-install.mjs:67execFile('reg.exe', - warningshellExec · shell
lib/dns-and-pid.mjs:70execFile('netstat', ['-ano', '-p', 'tcp'], { windowsHide: true, maxBuffer: 8 << 20 }, (err, stdout) => { - warningshellExec · shell
lib/dns-and-pid.mjs:120execFile('powershell', ['-NoProfile', '-NonInteractive', '-Command', cmd], { windowsHide: true, maxBuffer: 8 << 20 }, (err, stdout) => { - warningfsWrite · files
lib/hosts.mjs:86await fs.writeFile(HOSTS_PATH, next, 'utf8'); - warningfsWrite · files
lib/hosts.mjs:151await fs.writeFile(HOSTS_PATH, next, 'utf8'); - warningnetIp · network
lib/seed-nodes.mjs:63'https://223.5.5.5/resolve', - warningnetIp · network
lib/seed-nodes.mjs:64'https://1.12.12.12/resolve', - warningfsWrite · files
lib/storage.mjs:76await fs.writeFile(tmp, JSON.stringify(value, null, 2), 'utf8'); - warningfsWrite · files
lib/storage.mjs:130await fs.writeFile(this.file(name), pem, 'utf8'); - warningfsWrite · files
lib/storage.mjs:136await fs.writeFile(this.file(name), der); - warningshellExec · shell
lib/system-proxy.mjs:22execFile('reg.exe', args, { windowsHide: true, timeout, maxBuffer: 1 << 20 }, (error, stdout) => {
no dynamic conclusion (source harvest or model call failed) — no conclusion is not a pass; the overall rating falls back to the static tier.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
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-27 · activity: Active
• Repo created: 2026-10-27
• 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).
