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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.Install verification details →
Data as of (UTC)
What it doesAI
Harness mobile sync bundle with desktop plugin, relay server, and Android app for device pairing and notification forwarding.
- Desktop bridge plugin for Harness web profile with npm install
- Relay server with Docker/Caddy config and deployment guide
- Android APK with Flutter source, supports API 24+ and notification forwarding
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:kokubunshu/DSH-mobile-sync#v0.1.0+11Install method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.2-rc.3
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), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-03 · 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-02 → 11-03 · 7 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.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v0.1.0+11 | ○ | ○ | ○ | ○ | ○ |
v0.1.0+11github○ 16 ecosystem plugin2026-11-15
https://github.com/kokubunshu/DSH-mobile-sync
○dsh 0.2.2-rc.32026-11-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-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.2-rc.12026-11-06Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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-11-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-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.2.1-alpha.42026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@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.
○dsh 0.2.1-alpha.22026-10-12Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@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.1.7-rc.22026-09-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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-alpha.22026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@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-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@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-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@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-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@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-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/kokubunshu/DSH-mobile-sync#v0.1.0+11
ID: dsh-mobile-sync@v0.1.0+11@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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/dsh-mobile-sync/?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+11git2026-11-19v0.1.0+11same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/dbg-config-update.mjs:5const r = await fetch("http://127.0.0.1:3481/api/mbridge.state", { - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/inject-notify.mjs:14const API = "http://127.0.0.1:3610"; - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/notify-monitor.mjs:12const API = "http://127.0.0.1:3610"; - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/probe-events.mjs:10const API = "http://127.0.0.1:12574"; - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/probe-intents.mjs:9const API = process.env.API || "http://127.0.0.1:11716/api"; - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/send-plan-task.mjs:7const API = process.env.API || "http://127.0.0.1:11716/api"; - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/verify-envelope.mjs:9const stateRes = await fetch(`http://127.0.0.1:${PORT}/api/mbridge.state`, { - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/verify-mux.mjs:11["POST /m/api/workspace.list", fetch("http://127.0.0.1:8545/m/api/workspace.list", { - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/verify-mux.mjs:15["POST /m/api/session.list", fetch("http://127.0.0.1:8545/m/api/session.list", { - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/verify-mux.mjs:19["GET /m/api/events.mux", fetch("http://127.0.0.1:8545/m/api/events.mux", { headers: { cookie } })], - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/verify-plugin-fix.mjs:17const res = await fetch("http://127.0.0.1:8545/m/api/workspace.list", { - warningnetIp · network
01-harness-plugin/dsh-mobile-bridge/scripts/verify-session-fields.mjs:10const stateRes = await fetch(`http://127.0.0.1:${PORT}/api/mbridge.state`, {
show 3 audit findings
- mediumBridge pairing codes hardcoded as fallback defaults in probe scripts
01-harness-plugin/dsh-mobile-bridge/scripts/inject-notify.mjs:1332-hex-character pairing codes are committed to source as the default value used when CODE is unset. The same pattern appears in notify-monitor.mjs (line 13, same code), probe-events.mjs ("0ec8142ce143754fad1beeb5bab7129f") and simulate-app-mobilejs.mjs ("af39d3fb340f80741ca9ebc77b8de00e"). These values are the secret required to pair a device with the LAN bridge; anyone reading the repository can attempt pairing against a host still using the same code, and the presence of three distinct captured codes suggests they were harvested from real sessions rather than invented.
- mediumScripts auto-approve their own device pairing via the local control API without user consent
01-harness-plugin/dsh-mobile-bridge/scripts/inject-notify.mjs:32On receiving pair.pending the script immediately POSTs its own deviceId to the bridge's approve endpoint, turning the interactive pairing gate into a no-user-action flow; the same pattern is in notify-monitor.mjs, probe-events.mjs and probe-intents.mjs. Once approved, the socket can subscribe to event.session and tunnel http.request/rpc.request frames, so any local process able to reach the control API can pair itself and then drive the agent (e.g. session.create with a chosen cwd, session.prompt with arbitrary content) — see send-plan-task.mjs line 27 and the rpc.request frame in dbg-config-u
- lowDeveloper's absolute Windows path hardcoded in a script that creates agent sessions
01-harness-plugin/dsh-mobile-bridge/scripts/send-plan-task.mjs:27Discloses a local username and directory layout in a public repository, and the script creates a session rooted at that fixed directory, so it only works on the author's machine and silently picks a workspace if such a path exists on another host.
Only dev/probe scripts were harvested (no runtime lib/manifest); main issues are hardcoded bridge pairing codes and scripted auto-approval of device pairing.
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-16
• Stars: ★ 3 · 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-sync?
DSH-mobile-sync 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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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-sync?
Run dsh plugin --profile web add github:kokubunshu/DSH-mobile-sync#v0.1.0+11 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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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.
