Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
What it does
The real DeepSeek Harness Desktop UI on your iPhone, over Tailscale. No second Host, no reimplementation.
Installation
dsh plugin --profile web add github:Adolanium/dsh-phone#v1.0.0Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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.2.1-rc.2 current | dsh 0.2.1-alpha.4 |
|---|---|---|
| v1.0.0 | ○ | ○ |
v1.0.0github○ 2 ecosystem plugin2026-10-19
https://github.com/Adolanium/dsh-phone
○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Adolanium/dsh-phone#v1.0.0
ID: dsh-phone-5@v1.0.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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.42026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/Adolanium/dsh-phone#v1.0.0
ID: dsh-phone-5@v1.0.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-phone-5/)`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 low — stricter wins → overall low.
v1.0.0v1.0.0git2026-10-21v1.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (3)
- criticalshellExec · shell
packages/dsh-plugin-phone-bridge/lib/tailscale.js:157const result = await exec(binary, ['status', '--json'], { - warningfsWrite · files
packages/dsh-plugin-phone-bridge/lib/store.js:287await fs.writeFile(temporary, payload, { mode: 0o600 }) - warningfsWrite · files
packages/dsh-plugin-phone-bridge/lib/store.js:290await fs.chmod(this.path, 0o600)
show 2 audit findings
- lowRuntime imports vendored QR encoder whose source was not part of the audit bundle
packages/dsh-plugin-phone-bridge/lib/qr.js:13qr.js is loaded by routes.js for the GET /phone-bridge/qr.svg admin route, so ./qr/vendor/index.js executes inside the Host process, yet it was not harvested (NOT_HARVESTED claims none). Any network, filesystem or eval behaviour in that vendored code would be invisible to this audit; its only input is the pairing payload string, which bounds the damage.
- lowAdmin path prefix is the only barrier for proxied requests; proxy forwards x-dsh-phone-admin and rewrites Origin to loopback
packages/dsh-plugin-phone-bridge/lib/proxy.js:72adminGuard (routes.js:27-34) admits any request whose socket peer is loopback, that carries 'x-dsh-phone-admin: 1', and whose Origin is absent or equals the Host origin - all three are satisfiable by a paired phone through the proxy, which forwards arbitrary headers, connects from 127.0.0.1 and substitutes the loopback Origin. The only thing stopping it is index.js:64 isAdminPath(). Because the check and the upstream receive the same WHATWG-normalized pathname, this is currently not exploitable; it becomes reachable pairing-code/device-list disclosure if the Host router ever decodes or case-fo
Refuted the scanner's critical: execFile uses fixed argv with no shell, the listener binds only a 100.64/10 tailnet address, and pairing/device auth is sound; only two low hardening gaps remain.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-10-17 · activity: Active
• Repo created: 2026-10-17
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/Adolanium/dsh-phone
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
