dsh-mobile-pairing

DSH Mobile Remote pairing plugin

PluginNetwork

Verification

L4 · Install tested

stale

Risk

LowRisk

Health

Stable

Trust

Silver

Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.1.7-rc.2 · last checked 09-26Install verification details →

What it doesAI

DSH Mobile pairing plugin: secure pairing, loopback gateway, WebRTC Direct and encrypted tunnel fallback for host-mobile remote access.

Per-process pairing management with five-minute single-use v4 offers
Loopback-only host gateway; WebRTC Direct and encrypted tunnel fallback
No TURN, CDN, or maintainer-domain dependency; relay forwards ciphertext

networkAI

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:NOirBRight/dsh-mobile-pairing#v0.1.22

security scan passed · source release v0.1.22

Install method: GitHub · sandbox install ok, web smoke failed (L5) · verified on dsh 0.1.7-rc.2

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

Declared DSH compatibilityfrom package.json · peerDependencies

only the declared range >=0.1.7-alpha.2

Based on 1 requirement(s) across 2 @deepseek-ai/dsh-* packages.

raw ranges

>=0.1.7-alpha.2 ×2

✓ Running dsh 0.2.1-rc.2 is within the declared range — install is not blocked by version.

Whether it actually runs is a separate question → see the measured matrix below (L1–L5).

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)

At-a-glance → evidence in the cards below

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
v0.1.22	·	·	·	·	·
v0.1.19	✗	·	·	·	·
v0.1.16	·	·	·	·	·
v0.1.15	·	·	·	·	·

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

v0.1.22github2026-10-18

https://github.com/NOirBRight/dsh-mobile-pairing

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

v0.1.19github1 failed2026-09-26

github:NOirBRight/dsh-mobile-pairing#v0.1.19

✗dsh 0.1.7-rc.22026-09-26L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.1.7-rc.2
• Plugin artifact: github · github:NOirBRight/dsh-mobile-pairing#v0.1.19#v0.1.19

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Failed

Sandbox install failed

L5 · failed

ID: dsh-mobile-pairing@v0.1.19@dsh0.1.7-rc.2 · profile: l5-web-smoke

Issued: 2026-09-26 · expires: 2026-12-25

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-18

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-26

spec github:NOirBRight/dsh-mobile-pairing#v0.1.19 · channel GitHub source · install mode reused L4 scratch

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-26

spec github:NOirBRight/dsh-mobile-pairing#v0.1.19 · channel GitHub source · install mode reused L4 scratch

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-26

spec github:NOirBRight/dsh-mobile-pairing#v0.1.19 · channel GitHub source · install mode reused L4 scratch

L5 · Run tested✕ Failed

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-26

spec github:NOirBRight/dsh-mobile-pairing#v0.1.19 · install mode reused L4 scratch

check took: 0ms

Web boot readyL5.2_WEB_BOOT_READY✕ Failed

plugin tree failed to load

HTTP endpoint servedL5.3_HTTP_SERVED✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

v0.1.16github2026-09-20

https://github.com/NOirBRight/dsh-mobile-pairing

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

v0.1.15github2026-09-11

https://github.com/NOirBRight/dsh-mobile-pairing

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 official badges in your README to showcase security & install-test status:

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.

dsh-mobile-pairingAutomated review · daily

Static low; dynamic no conclusion (static stands) → overall low.

static low→dynamic no conclusion→overall low

vet findings0 critical·0 high

lowoverall · low

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin versionv0.1.22dsh manifest

scanned versionv0.1.22git2026-10-25

current versionv0.1.22same version

vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

2dynamic auditmodel reads redacted source context · never executes plugin code

not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.

Rule (2026-10-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. 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 static/vet.

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-09-25 · activity: Stable

• Repo created: 2026-08-21

• Stars: ★ 0 · Forks: 0

• Health: Stable — committed within 90 days

Source

GitHub: github.com/NOirBRight/dsh-mobile-pairing

Plugin notes

What is the dsh-mobile-pairing DeepSeek Harness plugin?

dsh-mobile-pairing is a DeepSeek Harness plugin maintained by @NOirBRight. It is cataloged on dsh.so as a Network plugin, with a public GitHub source, declared install command, and automated static scan results; plugins static-flagged at warn or above also carry a model-driven dynamic security audit record.

How do I install dsh-mobile-pairing?

Run dsh plugin --profile web add github:NOirBRight/dsh-mobile-pairing#v0.1.22 in a DeepSeek Harness (dsh) environment. This exact command has been verified by a real install inside an isolated windows-acl sandbox (L4).

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 (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above; when it reaches a conclusion that conclusion is authoritative for the combined verdict — it may raise or lower it — and the static/vet fused verdict applies only when there is none. Exemptions stay manual: the audit never writes the suppression list. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-10-03

dsh-mobile-pairing

What it doesAI

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README