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
SSH cloud connector: manage servers, port tunnels, and remote commands from DSH GUI and chat.
- Visual SSH connection manager with persisted config
- Port tunneling maps remote services to localhost
- Chat tools: remote exec, scp transfer, GPU monitor
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:gzr123166/dsh-cloud-connectorInstall 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.
9 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-16 · 9 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
09-24 → 11-16 · 8 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.1.0-rc.6 ×3
✗ Running dsh 0.2.2-rc.3 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-cloud-connector@1.0.0 0.2.2-rc.3 (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 |
|---|---|---|---|---|---|
| f8919d | ✗ | ✗ | ✓ | ✓ | ✓ |
| e40ea0 | · | · | · | · | · |
f8919dgithub✓ 13 runtime-verified◐ 1 testing2 failed2026-11-14
https://github.com/gzr123166/dsh-cloud-connector
✗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/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@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/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@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-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
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.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.1.7-rc.22026-09-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-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.1.7-rc.12026-09-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-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.1.3-alpha.22026-09-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-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.
✓dsh 0.1.3-alpha.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.2-rc.12026-09-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector#f8919d
ID: dsh-cloud-connector@f8919d@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-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.
✓dsh 0.1.2-alpha.12026-09-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@dsh0.1.2-alpha.1 · profile: l3-fullscan
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
active in loader tree (149 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◐dsh 0.1.1-rc.22026-08-28L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.1.1-rc.2
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector#f8919d
ID: dsh-cloud-connector@f8919d@dsh0.1.1-rc.2 · profile: l3-fullscan
Issued: 2026-08-28 · expires: 2026-09-04
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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/gzr123166/dsh-cloud-connector (version unstated)
ID: dsh-cloud-connector@f8919d@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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.
e40ea0github2026-08-24
https://github.com/gzr123166/dsh-cloud-connector
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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-cloud-connector/?ref=badge)``[](https://www.dsh.so/artifact/dsh-cloud-connector/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-cloud-connector/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-cloud-connector/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-cloud-connector/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-cloud-connector/?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 critical (authoritative when present) → overall critical.
v1.0.0dsh manifest1.0.0git2026-11-181.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (9)
- criticalsshWrite · destructive
lib/client.esm.js:151privateKey: (initial && initial.privateKey) || 'C:/Users/linxianyuan/.ssh/id_rsa_cloud', - criticalsshWrite · destructive
lib/client.esm.js:201React.createElement('input', { className: 'csc-input', value: form.privateKey, placeholder: 'C:/Users/linxianyuan/.ssh/id_rsa_cloud', onChan - criticalsshWrite · destructive
lib/client.js:156privateKey: (initial && initial.privateKey) || 'C:/Users/linxianyuan/.ssh/id_rsa_cloud', - criticalsshWrite · destructive
lib/client.js:206React.createElement('input', { className: 'csc-input', value: form.privateKey, placeholder: 'C:/Users/linxianyuan/.ssh/id_rsa_cloud', onChan - criticalshellExec · shell
lib/index.js:58const stdout = execSync(buildSshCmd(conn, remoteCmd), { - criticalshellExec · shell
lib/index.js:289execSync(scpCmd, { encoding: 'utf8', timeout: 300000, stdio: ['ignore', 'pipe', 'pipe'] }) - criticalsshWrite · destructive
lib/index.js:26privateKey: 'C:/Users/linxianyuan/.ssh/id_rsa_cloud', - warningchildProcess · code-exec
lib/index.js:119child = spawn('ssh', args, { stdio: 'ignore', windowsHide: true }) - warningbase64Decode · obfuscation
lib/index.js:52const remote = `echo ${encoded} | base64 -d | bash`
show 6 audit findings
- criticalShell command injection: host/username/privateKey from request body interpolated unquoted into local ssh command
lib/index.js:53buildSshCmd interpolates conn.username, conn.host, conn.port and conn.privateKey (all taken verbatim from normalizeConfig / normalizeConfig(body)) into a string passed to execSync, which executes through a shell. A username such as `x@y; <local command> #` or a host containing shell metacharacters runs arbitrary commands as the DSH process user. The same parameter path is reachable from the unauthenticated POST /cloud-connector/connect route and from the cloud_connect/cloud_manage_servers tools, so no legitimate-user interaction is required once the route is reachable.
- highUnauthenticated embedded HTTP route can trigger SSH actions and returns stored credentials
lib/index.js:499The handler performs no authentication, session or Origin check and readBody parses JSON regardless of Content-Type, so a simple cross-site POST (text/plain) from any web page the user visits, or any local process, can call /cloud-connector/connect to make the host run ssh with attacker-chosen parameters (feeding the injection above), add/remove servers, and start/stop tunnels. GET /cloud-connector/state returns statePayload(), which spreads every stored server object including privateKey and password, disclosing credentials in cleartext to any caller that can reach the web server.
- mediumServer configs (private key path, plaintext password) persisted to a hardcoded absolute path outside the plugin
lib/index.js:17normalizeConfig keeps the password and doConnect/cloud_manage_servers/HTTP /add push `{ ...conn, id }` into servers, which saveStore writes verbatim to servers.json. Credentials therefore sit in cleartext in a fixed directory that is unrelated to the plugin installation (and is writable/tamperable by any program that can write F:/ai软件/...), and the file is fed back to the API/UI and auto-connect logic at startup. The password field is also never used to build the ssh command (only privateKey is), so password-only servers cannot connect while still leaking the password to disk.
- mediumSSH host key verification disabled on every connection, tunnel and scp path
lib/index.js:111StrictHostKeyChecking=no makes ssh/scp accept any host key, so a network attacker (or a DNS/ARP-spoofed host) can impersonate the target server, capture the session and the local port-forwarded traffic, and return forged command output (which the model then reasons over). This is reachable on every connect, tunnel start/restore and transfer call.
- lowscp local/remote paths interpolated into a shell command with only double quotes
lib/index.js:286The paths come from tool arguments and are only wrapped in double quotes; on a POSIX shell `$(...)`/backticks still expand inside double quotes, so a crafted localPath executes a local command. Impact is limited because the plugin is Windows-oriented (cmd.exe does not expand $()) and cloud_exec already gives arbitrary remote command execution by design.
- lowDeveloper-specific absolute paths, default server IP and private key path hardcoded
lib/index.js:26The plugin breaks on any machine other than the author's, leaks the author's username, local directory layout and a real cloud host, and silently offers an unrelated remote server as the default connect target for cloud_connect.
Host half builds local ssh/scp shell strings from unsanitized host/username and exposes connect plus stored credentials via an unauthenticated HTTP route: local command injection risk.
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-08-15 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 0 · Forks: 0
• Health: Inactive — no commit in 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-cloud-connector?
dsh-cloud-connector 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-cloud-connector?
Run dsh plugin --profile web add github:gzr123166/dsh-cloud-connector 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-18 (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.
