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 →
Data as of (UTC)
What it doesAI
Android app that bootstraps Termux and deploys DeepSeek Harness with one tap, including a built-in browser and storage management.
- Tap-only install and setup, no command line required
- Termux bootstrap and one-click deployment
- Built-in browser and storage management
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:Jensen-Yao/deepseek-harness-android-app#v1.2Install method: GitHub · runtime test inconclusive (L5 unknown) · 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.
current (registry 2026-11-13) · 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○ 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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| v1.2 | ○ | ○ | ○ | ○ | ○ |
v1.2github○ 15 ecosystem plugin1 failed2026-11-14
https://github.com/Jensen-Yao/deepseek-harness-android-app
○dsh 0.2.2-rc.12026-11-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
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-rc.52026-10-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-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.2.1-rc.32026-10-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-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.2.1-rc.22026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.2.1-rc.2 · 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.
○dsh 0.2.1-alpha.42026-10-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
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.32026-10-15Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.3
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.2.1-alpha.3 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
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-10Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-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.2.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@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-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@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.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.1.6-alpha.2 · profile: l4-sandbox
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-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-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.1.5-rc.22026-09-13Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-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.1.3-alpha.12026-09-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@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.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Jensen-Yao/deepseek-harness-android-app#v1.2
ID: deepseek-harness-android-app@v1.2@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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.
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/deepseek-harness-android-app/?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.2git2026-11-14v1.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningchildProcess · code-exec
daemon/server.mjs:70const child = spawn(DSH_BIN, ['web'], { - warningshellExec · shell
daemon/server.mjs:116dshVersion = String(execFileSync(DSH_BIN, ['--version'], { timeout: 15000 })).trim(); - warningshellExec · shell
daemon/server.mjs:159try { node = String(execFileSync(PREFIX + '/bin/node', ['-v'], { timeout: 10000 })).trim(); } catch { /* ignore */ } - warningshellExec · shell
daemon/server.mjs:162const out = String(execFileSync(PREFIX + '/bin/df', ['-h', HOME], { timeout: 10000 })); - warningnetIp · network
daemon/server.mjs:124const url = new URL(req.url, 'http://127.0.0.1'); - warningfsWrite · files
daemon/server.mjs:321fs.writeFileSync(f, body, 'utf8'); - warningnetIp · network
daemon/start-daemon.sh:4if ! curl -s --max-time 2 http://127.0.0.1:8023/api/ping >/dev/null 2>&1; then
show 7 audit findings
- highUnauthenticated loopback control API lets any local app or web page start/stop/kill the DSH process
daemon/server.mjs:398The HTTP handler never checks a token, session or Origin header, yet /api/start, /api/stop and /api/restart spawn and SIGKILL dsh processes (stopDsh escalates to SIGKILL). Any app on the device with INTERNET permission, or any web page the user visits (simple cross-origin GET/POST to 127.0.0.1:8023 requiring no preflight), can stop the agent, restart it, or loop restarts for denial of service.
- highUnauthenticated /api/write can overwrite ~/.dsh MCP config and the daemon's own server.mjs, giving persistent code execution
daemon/server.mjs:322safePath allows any path under HOME/.dsh, HOME/dsh and HOME/deepseek-harness-android, and the body is written verbatim. An attacker can replace ~/.dsh/mcp.json (the exact file this daemon treats as the MCP config, line 221-224) with a malicious server command, or overwrite the daemon script itself at ~/dsh/control/server.mjs, then call /api/restart or wait for restart-daemon.sh. The next launch executes attacker-controlled code as the Termux user.
- mediumUnauthenticated /api/read and /api/logs expose DSH configuration and logs that may contain credentials
daemon/server.mjs:310Any local caller can read every file under ~/.dsh (config, mcp.json, session/workspace files) and the dsh log, which commonly contains API keys, tokens or prompts. Combined with the unauthenticated surface this is a straightforward credential-exfiltration channel for a co-resident app or drive-by web request.
- mediumStorage relocation path check is bypassable with '..', allowing cp/rm/symlink outside the intended roots
daemon/server.mjs:272The prefix test does not resolve '..' segments, so to=/data/data/com.termux/files/home/../../.. passes and is then used for fs.mkdirSync, `cp -a def/. to/` and fs.symlinkSync (also /sdcard/../.. in set-storage-all). An unauthenticated caller can create directories/symlinks in and copy data to arbitrary locations writable by the Termux user, outside the documented storage roots.
- mediumdsh is always started with DSH_PERMISSION_MODE=danger-full-access, disabling its permission model
daemon/server.mjs:76Every start triggered by the daemon (including the unauthenticated /api/start and /api/restart endpoints) launches the DSH agent with full tool/filesystem/command permissions and no user confirmation, so any caller that can start the agent obtains an unrestricted agent rather than the default sandboxed mode.
- mediumstart-daemon.sh silently launches sshd, opening a remote-access service on the device
daemon/start-daemon.sh:12Starting the control daemon (and restart-daemon.sh, which calls this script) also brings up an SSH server with no disclosure, no configuration shown and no consent step. This creates an additional network-exposed entry point to the Termux home that is independent of the localhost control API and outside the plugin's stated purpose.
- lowState-changing endpoints accept GET and no Origin/Host check is performed
daemon/server.mjs:145/api/start, /api/stop, /api/restart, /api/logs, /api/read act on GET with no method or Origin restriction, so a malicious web page can trigger them with an <img>/fetch no-cors request or via DNS rebinding against 127.0.0.1:8023. This is the delivery vector that makes the unauthenticated findings reachable from a browser.
Unauthenticated loopback control API with file write into ~/.dsh and ~/dsh lets any local app or web page overwrite MCP/daemon files and restart dsh, achieving persistent code execution.
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-16 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 23 · Forks: 1
• 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 deepseek-harness-android-app?
deepseek-harness-android-app is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 deepseek-harness-android-app?
Run dsh plugin --profile web add github:Jensen-Yao/deepseek-harness-android-app#v1.2 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-14 (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.