Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Adds a VS Code-style right-click menu to the DSH Web UI sidebar file tree: copy absolute/relative paths or names, reveal in Explorer/Finder, and open with the default app.
- Right-click file tree menu with copy absolute/relative path and name
- Reveal files in Explorer or Finder, or open with the default program
- Takes over the built-in files tab in place without adding a new tab
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.
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling (a rotating daily shard); the npm pair from every snapshot.
7 samples (roughly every 7 days), 4 of them reconstructed (hollow dots); sampled points, not a daily series
09-17 → 10-28 · 7 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
09-24 → 10-28 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:yudaxia1/dsh-sidebar-file-menuInstall method: GitHub · sandbox install ok, web smoke failed (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.5 current | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 444f4b | ✗ | ✗ | ✗ | ✗ | ✗ |
444f4bgithub11 failed2026-10-31
https://github.com/yudaxia1/dsh-sidebar-file-menu
✗dsh 0.2.1-rc.5current2026-10-31L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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-rc.32026-10-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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.42026-10-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.12026-09-29L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-rc.22026-09-25L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-rc.12026-09-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.6-alpha.22026-09-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.6-alpha.12026-09-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/yudaxia1/dsh-sidebar-file-menu (version unstated)
ID: dsh-sidebar-file-menu@444f4b@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-file-menu/?ref=badge)`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 low (authoritative when present) → overall low.
v0.1.0dsh manifest0.1.0git2026-11-010.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalnewFunction · code-exec
verify-render.mjs:85new Function('require', source)(tableRequire) - criticalnewFunction · code-exec
verify.mjs:82new Function('require', entrySource)(tableRequire)
show 2 audit findings
- lowDev-only harness evaluates a caller-supplied file path with new Function
verify.mjs:82Running the harness with an arbitrary path executes that file's contents in the Node process. It is a developer smoke test, is excluded from package.json's "files" list, has no npm scripts entry, and is never loaded by the shell, so there is no runtime reachable impact.
- lowHost-side native opener (explorer/open/xdg-open) cannot be line-audited from the harvested source
verify-host.mjs:11The plugin's core capability is launching a native file manager or default application for a path inside the Session workspace. Only the client half and the author's own test harnesses are available here, so nothing confirms that the path is passed as an argv element rather than interpolated into a shell string. Given a filename containing quotes or '&', string interpolation would be command injection; no such code is visible either way.
Client half is a plain React UI; the flagged criticals are a dev-only harness evaluating a local bundle and the plugin's by-design native file open, so no runtime risk was found.
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-09-16 · activity: Stable
• Repo created: 2026-09-16
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 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-file-menu?
dsh-sidebar-file-menu 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-file-menu?
Run dsh plugin --profile web add github:yudaxia1/dsh-sidebar-file-menu in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed yet.
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-11-01 (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.