This repository has been renamed: harryopo/dsh-cloud-workspaces — click to visit the new location. Everything below is preserved as originally indexed.
Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.0-rc.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
SSH Remote IDE for DeepSeek Harness: remote development via SSH/SFTP with live terminal.
- Connect via SSH to make IDE remote
- Browse server files over SFTP
- Live SSH PTY terminal
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:harryopo/dsh-remote-ide#v0.3.0Install method: GitHub · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.0-rc.2
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.
current (registry 2026-11-13) · 3 samples (roughly every 1 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 10-05 · 3 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
Only 1 points (< 3): no chart yet
10-05 → 10-05 · 1 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 8 @deepseek-ai/dsh-* packages. raw ranges
^0.1.1-rc.2 ×8
✗ Running dsh 0.2.2-rc.2 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-remote-ide@0.3.0 0.2.2-rc.2 (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.0-rc.2 | dsh 0.1.7-rc.2 | dsh 0.1.7-rc.1 | dsh 0.1.6-alpha.2 | dsh 0.1.6-alpha.1 |
|---|---|---|---|---|---|
| v0.3.0 | ✗ | ✗ | · | · | · |
v0.3.0github3 failed2026-10-09
https://github.com/harryopo/dsh-remote-ide
✗dsh 0.2.0-rc.22026-10-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/harryopo/dsh-remote-ide#v0.3.0
ID: dsh-remote-ide@v0.3.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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/harryopo/dsh-remote-ide#v0.3.0
ID: dsh-remote-ide@v0.3.0@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.
✗prehistory2026-09-30L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/harryopo/dsh-remote-ide#v0.3.0
ID: dsh-remote-ide@v0.3.0@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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-remote-ide/?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.
v0.3.0dsh manifestv0.3.0git2026-10-08v0.4.0version moved onclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- criticalshellExec · shell
src/ssh-service.ts:73exec(command: string, options?: { timeoutMs?: number; cwd?: string }): Promise<ExecResult> - criticalsshWrite · destructive
src/store.ts:273keyPath: block.identityFile ?? '~/.ssh/id_ed25519', - warningshellExec · shell
src/store.ts:165execFileSync('icacls', [ - warningmanifest-fs-unfenced · sandbox
agent-presets/remote-legacy/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-fs-unfenced · sandbox
agent-presets/remote-legacy/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
agent-presets/remote-legacy/agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
agent-presets/remote-legacy/agent.cordis.ymlShell tool without a sandbox runner or policy in realm
show 2 audit findings
- mediumSSH login passwords are persisted in cleartext to ~/.dsh/dsh-remote-ide.json
src/store.ts:145Stored entries contain auth.password, so the cleartext login credential of every configured host lands on disk. POSIX 0600 is applied, but on Windows chmod is a documented no-op and tightenWindowsAcl() is best-effort inside a swallowed try/catch ('ACL 收紧失败不阻断保存'); the code's own comment states the inherited .dsh ACL lets sandbox-group processes read the cleartext password. Any process or backup that can read that file obtains credentials usable to log into the remote servers.
- lowService accessor hands the full host entry, including the cleartext password, to any in-process consumer
src/ssh-service.ts:222getStoredEntry() is a public member of the shared Service, so the guarantee that the password '绝不进 wire 面' rests only on every caller (index.ts, tools.ts and the typert endpoints, none of which are in the harvested set) redacting it. A single caller that forwards this object, or that serialises its own error/log context, exposes the cleartext credential; the neighbouring methods are typed as secret-free summaries while this one is not.
Static scan's 2 criticals are refuted: the bash -c/icacls execs are the plugin's designed SSH command path; the real issue is cleartext SSH password storage.
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-11-07 · activity: Active
• Repo created: 2026-08-14
• Stars: ★ 5 · Forks: 2
• 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-remote-ide?
dsh-remote-ide 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-remote-ide?
Run dsh plugin --profile web add github:harryopo/dsh-remote-ide#v0.3.0 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-13 (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.