Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Enhances the official DSH sidebar file view with source view, in-place editing, line-number toggle, search, and font zoom.
- Source view for files in the DSH sidebar
- In-place file editing without leaving the sidebar
- Toggle line numbers, search content, and zoom fonts
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-sidebar-plusInstall 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.3 current | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| 0.4.4 | ✓ | ✓ | ✗ | ✓ | ✓ |
| 0.4.3 | · | · | · | · | · |
| 0.4.2 | · | · | · | · | · |
| 0.4.1 | · | · | · | · | · |
| 0.4.0 | · | · | · | · | · |
0.4.4npm✓ 4 runtime-verified1 failed2026-10-26
dsh-sidebar-plus
✓dsh 0.2.1-rc.3current2026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-sidebar-plus@0.4.4
ID: dsh-sidebar-plus@0.4.4@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-sidebar-plus@0.4.4
ID: dsh-sidebar-plus@0.4.4@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.
✗dsh 0.2.1-alpha.42026-10-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-sidebar-plus@0.4.4
ID: dsh-sidebar-plus@0.4.4@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-sidebar-plus@0.4.4
ID: dsh-sidebar-plus@0.4.4@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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.0-rc.22026-10-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-sidebar-plus@0.4.4
ID: dsh-sidebar-plus@0.4.4@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
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.
0.4.3npm✓ 1 runtime-verified2026-10-05
dsh-sidebar-plus
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-sidebar-plus@0.4.3
ID: dsh-sidebar-plus@0.4.3@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
0.4.2npm✓ 1 runtime-verified2026-09-29
dsh-sidebar-plus
✓dsh 0.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-sidebar-plus@0.4.2
ID: dsh-sidebar-plus@0.4.2@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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.
0.4.1npm2026-09-28
dsh-sidebar-plus
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.4.0npm2026-09-27
dsh-sidebar-plus
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-sidebar-plus/?ref=badge)``[](https://www.dsh.so/artifact/dsh-sidebar-plus/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-sidebar-plus/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-sidebar-plus/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-sidebar-plus/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-sidebar-plus/?ref=badge-install)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
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 high (authoritative when present) → overall high.
v0.4.4dsh manifest0.4.4npm2026-10-290.4.4same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- criticalnewFunction · code-exec
lib/client.js:43const factory = new Function("ENV", '"use strict";' + String(code)); - criticalnewFunction · code-exec
lib/index.js:77const factory = new Function('fs', 'os', 'path', 'crypto', 'DSH_HOME', 'log', src) - warningfsWrite · files
hot-host.cjs:60fs.writeFileSync(tmp, JSON.stringify(obj, null, 2) + '\n', 'utf8'); - warningfsWrite · files
hot-host.cjs:199fs.writeFileSync(tmp, buf); - warningfsWrite · files
hot-host.cjs:300fs.writeFileSync(probe, 'ok');
show 4 audit findings
- high/dsh-sp/save overwrites any existing absolute path on the host; no workspace confinement
hot-host.cjs:181saveFile only requires an absolute path to an existing regular file (lstat, symlinks rejected) plus a string body up to 32MB. Given a precondition of issuing a same-origin (or Origin-less) HTTP request - any JS running in the DSH page, a malicious plugin, or any local process - an attacker can overwrite ~/.bashrc, ~/.ssh/authorized_keys, the harness's own config, or this plugin's own hot-host.cjs, turning page-level script execution into persistent host file write (the .bak copy makes it recoverable but does not prevent the write). Reachable from lib/index.js: handler() -> sub === '/save' -> h
- highhot-host.cjs is re-read and executed via new Function every 2s, so a write to it becomes Node code execution
lib/index.js:77The loader executes the raw file content in-process and re-executes it whenever the sha1 of hot-host.cjs changes (2s poll). Combined with finding #1 (or any local write to the plugin directory), an attacker replaces hot-host.cjs and gets code running inside the Node process with full fs/os/path/crypto; dynamic import() inside the injected body reaches node:child_process.execSync, i.e. arbitrary command execution on the host within ~2 seconds, surviving restarts until the file is restored.
- mediumClient compiles and executes JS fetched from /dsh-sp/pull with new Function, no integrity check
lib/client.js:43Every open page polls /dsh-sp/pull and evals the response body in the page context (swap/notifyBus) with no hash, signature or origin-of-file check. Any party able to influence that HTTP response or the hot-client.cjs file on disk (e.g. via finding #1) gets arbitrary code execution in the DSH page for all connected clients, and the payload is re-applied every 2s.
- lowOrigin guard fails open when the Origin header is absent; no authentication on /dsh-sp endpoints
lib/index.js:29requestRejection is the only gate and it allows any request without an Origin header (non-browser clients, curl, some embedded webviews). Reads such as GET /dsh-sp/stat?abs=<any path> then disclose existence/size/mtime of arbitrary host files, and /dsh-sp/mark//marks expose the in-memory marks store. POST /save and /config are protected against plain CSRF mainly by the JSON content-type requirement (CORS preflight), not by authentication; if the harness ever binds the web server beyond loopback, these become directly reachable.
Verified: /dsh-sp/save overwrites any existing absolute path, and hot-host.cjs is re-executed via new Function every 2s, so a same-origin caller gains host file write and Node code execution.
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-04 · activity: Active
• Repo created: 2026-09-15
• Stars: ★ 2 · Forks: 1
• 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).
Frequently asked questions
What is dsh-sidebar-plus?
dsh-sidebar-plus is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install dsh-sidebar-plus?
Run dsh plugin --profile web add dsh-sidebar-plus in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-10-29 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.