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
Serve DeepSeek Harness Web GUI to a phone via your domain and server with token gate and SSH reverse tunnel.
- Serve Web GUI to phone through own domain
- Token gate for access control
- Supervised SSH reverse tunnel
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:kk99668/dsh-mobile-accessInstall 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.
8 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-11 · 8 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-06 → 11-11 · 6 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-mobile-access-2@0.1.0-rc.6 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 |
|---|---|---|---|---|---|
| 6aff57 | · | · | · | · | · |
| 1a9c5f | ✗ | ✗ | ✗ | ✗ | ✗ |
6aff57github2026-08-24
https://github.com/kk99668/dsh-mobile-access
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
1a9c5fgithub◐ 1 testing17 failed2026-11-14
https://github.com/kk99668/dsh-mobile-access
✗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/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@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/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@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.2.0-rc.12026-09-30L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.2.0-rc.1 · profile: l4-sandbox
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.
✗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/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@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.
✗dsh 0.1.7-rc.12026-09-23L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.1.7-rc.1 · profile: l3-fullscan
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
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-13L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
View checks & evidence
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-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-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.3-alpha.12026-09-07L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access#1a9c5f
ID: dsh-mobile-access-2@1a9c5f@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dsh0.1.2-alpha.1 · profile: l3-fullscan
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
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/kk99668/dsh-mobile-access#1a9c5f
ID: dsh-mobile-access-2@1a9c5f@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-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/kk99668/dsh-mobile-access (version unstated)
ID: dsh-mobile-access-2@1a9c5f@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-mobile-access-2/?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.1.0-rc.6dsh manifest0.1.0-rc.6git2026-11-170.1.0-rc.6same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- criticalsshWrite · destructive
scripts/setup-server.sh:100} > "$RELAY_HOME/.ssh/authorized_keys" - criticalsshWrite · destructive
scripts/setup-server.sh:102chmod 600 "$RELAY_HOME/.ssh/authorized_keys" - criticalsshWrite · destructive
scripts/setup-server.sh:103echo " installed: $KEY_FILE -> $RELAY_HOME/.ssh/authorized_keys" - warningchildProcess · code-exec
src/index.ts:129spawnProcess: (bin, args) => spawn(bin, args, { stdio: ['ignore', 'ignore', 'pipe'] }), - warningchildProcessImport · code-exec
src/tunnel.ts:9import type { ChildProcess } from 'node:child_process'
show 5 audit findings
- mediumUnthrottled public token login on the gate (no rate limit or lockout)
src/gate.ts:200The gate is the only authentication layer for the publicly tunneled GUI. Any internet client can POST /_auth repeatedly (and probe Basic/Bearer on any path) with no rate limit, lockout or backoff, so the documented 8-character minimum token can be brute-forced; a success grants full control of the harness agent (arbitrary tool/command execution on the operator's machine).
- lowSSH relay host key accepted on first use (StrictHostKeyChecking=accept-new)
src/tunnel.ts:64The first connection to the relay is trust-on-first-use; an on-path attacker present at that moment can impersonate the relay and observe all tunneled traffic, including the token cookie and full GUI/API data.
- lowRelay authorized_keys lacks no-port-forwarding/restrict despite the "no other forwarding" claim
scripts/setup-server.sh:96permitlisten only constrains -R remote listens; the key can still open -L local forwards, so anyone who obtains the private key can use the relay as a proxy into its internal network, contradicting the script's stated restriction.
- lowAuth cookie carries the static token without Secure flag or expiry
src/gate.ts:211The long-lived shared secret is stored verbatim in a non-Secure cookie, so any cleartext http:// request to the public host (pre-redirect downgrade, HSTS-less clients) carries the token in the open; there is no session expiry or rotation, so a leaked cookie equals permanent agent control.
- lowRoot setup script trusts a remotely fetched apt signing key without fingerprint verification
scripts/setup-server.sh:57Executed as root, whatever that URL serves becomes the trusted signing key for the Caddy apt repository, so compromise or TLS interception of that host leads to root package installation on the relay server (this mirrors upstream Caddy docs but is still an unverified trust root).
No command injection or backdoor found: ssh is spawned with an argument array from validated config and the gate authenticates every path; residual risk is an unthrottled public token login plus SSH/cookie hardening gaps.
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-mobile-access?
dsh-mobile-access 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-mobile-access?
Run dsh plugin --profile web add github:kk99668/dsh-mobile-access 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.
