Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
What it does
Zero-token update checks for DSH plugins, DSH Desktop and core: live progress, one-click updates, DSH NEXT migration guard and per-version ignore.
Installation
dsh plugin --profile web add github:TT10-24/dsh-plugin-updater#v0.3.4Install 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.3.4 | ✓ |
v0.3.4github✓ 1 runtime-verified2026-10-28
https://github.com/TT10-24/dsh-plugin-updater
✓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/TT10-24/dsh-plugin-updater#v0.3.4
ID: dsh-plugin-updater-7@v0.3.4@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-plugin-updater-7/)``[](https://www.dsh.so/artifact/dsh-plugin-updater-7/)`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 (static stands) → overall low.
v0.3.6dsh manifestv0.3.6git2026-10-28v0.3.4version moved onclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (9)
- criticalnewFunction · code-exec
.check/drag-check.mjs:105new Function('window', source)(windowStub) - criticalnewFunction · code-exec
.check/render-check.mjs:93new Function('window', source)(windowStub) - warningfsWrite · files
.check/selfcheck.mjs:119fs.writeFileSync(path.join(sourceHome, 'profiles', 'desktop', 'package.json'), JSON.stringify({ name: 'dsh-profile-desktop', dependencies: { - warningfsWrite · files
.check/selfcheck.mjs:121fs.writeFileSync(path.join(sourceHome, 'sessions', 'one.jsonl'), '{"hello":"world"}\n') - warningfsWrite · files
.check/selfcheck.mjs:123fs.writeFileSync(path.join(sourceHome, 'storages', 'state.json'), '{"ok":true}\n') - warningchildProcessImport · code-exec
index.js:27import { execFile } from 'node:child_process' - warningfsWrite · files
index.js:140fs.writeFileSync(temporary, JSON.stringify(value), 'utf8') - warningfsWrite · files
index.js:350fs.writeFileSync(temporary, text, 'utf8') - warningfsWrite · files
index.js:634fs.writeFileSync(path.join(this.dataDir, 'restore-data-home.ps1'), this.restoreScript(destination), 'utf8')
not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.
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-28 · activity: Active
• Repo created: 2026-10-26
• Stars: ★ 1 · 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).
