Install verification: sandbox install failed (L4) · tested on dsh 0.1.7-rc.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Turns a PC into a server so mobile devices can access the local DeepSeek Harness Web UI with a mobile-optimized interface.
- Zero-dependency reverse proxy using Node.js standard library
- Automatic LAN address detection for easy access
- Injects mobile UI via server-side viewport, CSS, and JS
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:menghuanshiguang/dsh-mobileshareInstall method: GitHub · sandbox install failed (L4) · verified on dsh 0.1.7-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.
9 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-13 · 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
10-02 → 11-13 · 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.1.7-rc.2 | dsh 0.1.6-alpha.2 | dsh 0.1.6-alpha.1 | dsh 0.1.5-rc.2 | dsh 0.1.3-alpha.2 |
|---|---|---|---|---|---|
| v1.1.0 | · | · | · | · | · |
v1.1.0github2026-11-14
https://github.com/menghuanshiguang/dsh-mobileshare
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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-mobileshare/?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.
v1.1.0dsh manifestv1.1.0git2026-11-19v1.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningnetIp · network
src/index.js:266results.loopback = await probe('http://127.0.0.1:' + state.port); - warningnetIp · network
src/index.js:372const existing = await probe('http://127.0.0.1:' + port); - warningnetIp · network
src/index.js:452const handle = spawn([cf, 'tunnel', '--url', 'http://127.0.0.1:' + state.port, '--no-autoupdate'], { stdout: 'pipe', stderr: 'pipe' }); - warningfsWrite · files
src/index.js:191try { fs.writeFileSync(stateFile, JSON.stringify({ port: listenPort, user: authUser, pass: authPass, token: sessionToken })); } catch (e) {} - warningfsWrite · files
src/index.js:571const h = spawn([nodePath, '-e', 'const fs=require("fs"),os=require("os"),path=require("path");try{const f=path.join(os.homedir(),".dshm-sha
show 5 audit findings
- highPrivileged /dshm2-api routes have no CSRF/Origin/method checks and expose an auth:false switch that spawns an unauthenticated 0.0.0.0 proxy
src/index.js:535Every handler ignores the HTTP method and apiBody() parses the body regardless of Content-Type, so any web page the user visits can fire a simple GET or text/plain POST at the harness host (e.g. /dshm2-api/stop, /dshm2-api/firewall, /dshm2-api/list) and, with {"auth":false}, silently start a proxy on 0.0.0.0 whose authorized() returns true for all requests. Anyone on the LAN (or the public cloudflared tunnel) then gets unauthenticated control of the harness, which executes commands on the host. Precondition: the host web server does not add its own Origin/Host enforcement (none visible in this
- mediumShare is silently restored from ~/.dshm-share.json on every harness start, including with authentication disabled
src/index.js:504restoreShare() runs unconditionally at plugin load, so once the LAN/Internet listener has been enabled it is re-created on every harness start without user confirmation. If the persisted password is empty (a state file written by an auth:false session), start() receives auth:false and brings back a completely unauthenticated 0.0.0.0 proxy.
- medium/dshm2-api/list, /mkdir and /pick accept arbitrary absolute paths over the same password-protected proxy
src/index.js:544The routes pass the caller-supplied path straight into node -e subprocesses with no restriction to the selected workspace roots, and they are reachable through the LAN/cloudflared proxy as well as locally. Any holder of the share password (or any request when auth is off) can enumerate the whole disk and create a harness workspace at any directory, widening the agent's file scope without further confirmation.
- lowShare password and session token are stored in plaintext in the home directory; token (Math.random) bypasses Basic auth
src/index.js:191~/.dshm-share.json holds the proxy password and an authentication-bypass token in plaintext (default file mode). The 24-char token is generated with Math.random (not a CSPRNG) and compared with === in authorized(), so any local reader or backup/sync tool obtains lasting access to the LAN-facing, code-executing UI.
- lowInbound firewall rule is added automatically and only removed on explicit stop; a crashed proxy leaves the port open
src/index.js:326Every start() (and every /dshm2-api/firewall call, which a cross-site request can trigger) tries to open the inbound port; removeFirewallRule() is only invoked from stop(). If the proxy crashes or the host is killed, the allow rule persists, leaving the port reachable for later, possibly unrelated, listeners.
Privileged /dshm2-api routes lack CSRF/origin checks and can run the proxy unauthenticated on 0.0.0.0; credentials persist in plaintext and filesystem APIs accept arbitrary paths.
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-mobileshare?
dsh-mobileshare 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-mobileshare?
Run dsh plugin --profile web add github:menghuanshiguang/dsh-mobileshare#v1.1.0 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.
