Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
DSH Web UI plugin to drag a conversation onto any workspace to organize it.
- Drag-and-drop conversations onto workspace groups
- Moves cwd, files, and registry on drop
- Organizes DSH sessions into workspaces
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 github:lanscer/dsh-workspace-drag#v1.1.1Install method: GitHub · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
7 samples (roughly every 5 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-16 · 7 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
10-02 → 11-16 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
Only 0 points (< 3): no chart yet
no data yet
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
Based on 1 requirement(s) across 3 @deepseek-ai/dsh-* packages. raw ranges
>=0.0.1-rc.1 <0.1.0 || >=0.1.0-rc.1 <0.1.1-0 || >=0.1.1-rc.1 <0.2.0-0 ×3
✗ Running dsh 0.2.2-rc.5 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-workspace-drag@1.1.1 0.2.2-rc.5 (the exemption lives in the local profile; this site does not assume one)
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin \ dsh | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| v1.1.1 | ✗ | ✗ | ✗ | ✗ | ✗ |
v1.1.1github10 failed2026-11-14
https://github.com/lanscer/dsh-workspace-drag
✗dsh 0.2.1-rc.52026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/lanscer/dsh-workspace-drag#v1.1.1
ID: dsh-workspace-drag@v1.1.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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.2.1-rc.32026-10-26L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/lanscer/dsh-workspace-drag#v1.1.1
ID: dsh-workspace-drag@v1.1.1@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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.2.1-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/lanscer/dsh-workspace-drag#v1.1.1
ID: dsh-workspace-drag@v1.1.1@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 · github:lanscer/dsh-workspace-drag#v1.1.1#v1.1.1
ID: dsh-workspace-drag@v1.1.1@dsh0.2.1-alpha.4 · profile: l5-web-smoke
Issued: 2026-10-16 · expires: 2027-01-14
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/lanscer/dsh-workspace-drag#v1.1.1
ID: dsh-workspace-drag@v1.1.1@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/lanscer/dsh-workspace-drag#v1.1.1
ID: dsh-workspace-drag@v1.1.1@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/lanscer/dsh-workspace-drag#v1.1.1
ID: dsh-workspace-drag@v1.1.1@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-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/lanscer/dsh-workspace-drag#v1.1.1
ID: dsh-workspace-drag@v1.1.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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-alpha.22026-09-23L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/lanscer/dsh-workspace-drag#v1.1.1
ID: dsh-workspace-drag@v1.1.1@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/lanscer/dsh-workspace-drag#v1.1.1
ID: dsh-workspace-drag@v1.1.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-workspace-drag/?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 medium (authoritative when present) → overall medium.
v1.1.1dsh manifestv1.1.1git2026-11-19v1.1.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalshellExec · shell
lib/index.js:222const found = execSync('which zstd', { encoding: 'utf8', stdio: ['pipe', 'pipe', 'ignore'] }).trim() - warningshellExec · shell
lib/index.js:249return execFileSync(ZSTD_BIN, args, {
show 4 audit findings
- mediumMove route recursively deletes the source session directory after only a heuristic quiescence check
lib/index.js:605The move path copies the session dir to a temp staging dir, rewrites logs, verifies only the header line (rewrittenHeader.cwd === targetPath && rewrittenHeader.id === sessionId, lib/index.js:592) and then irreversibly deletes the original directory. The quiescence gate can return ok as soon as two mtime samples 250 ms apart are equal (lib/index.js:442-448), so a session that is still appending at >250 ms intervals (e.g. an agent whose status is not reported as 'running', or one that starts writing right after the check) can have events appended between the copy and the rmSync; those bytes exis
- lowState-changing move route has no plugin-level authorization or origin check
lib/index.js:720POST /api/dsh-workspace-drag/move accepts {sessionId,targetWorkspaceId,waitMs} and physically relocates (and deletes) session storage, yet the handler only checks the method and the persisted enabled flag. The plugin therefore relies entirely on the host webServer for authentication/CSRF/CORS enforcement; if a deployment exposes those routes without that gate, any client able to reach the port can move or trigger deletion of session data.
- lowRequest sessionId is interpolated into a filesystem path without validation
lib/index.js:504sessionId comes straight from the JSON body and is used in join() while scanning the sessions root, so '../' segments escape the sessions tree and make the plugin stat, read and stage arbitrary locations that happen to contain a file named session*.jsonl. The later identity check (rewrittenHeader.id !== sessionId at lib/index.js:592) prevents the destructive rmSync from running on such a directory, and parse errors echo fragments of the input back to the caller, so this is a hardening gap rather than an exploitable primitive today.
- lowzstd CLI is resolved at module load, aborting plugin (and possibly profile) bootstrap
lib/index.js:242findZstd() throws 'zstd CLI not found' when the binary is absent, and because it runs at import time the whole module fails to evaluate even when only plaintext session logs exist; in a bundled web profile that can break plugin loading beyond this plugin. The PATH probe itself uses execSync('which zstd') with a constant string, which is not injectable.
No RCE or secret leaks; real risk is an HTTP-triggered session move that recursively deletes the source log dir after only heuristic quiescence, with no in-plugin auth.
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-25 · activity: Stable
• Repo created: 2026-08-20
• Stars: ★ 1 · 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-workspace-drag?
dsh-workspace-drag 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-workspace-drag?
Run dsh plugin --profile web add github:lanscer/dsh-workspace-drag#v1.1.1 in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run 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-19 (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.
