@dsh-remote/protocol

Wire protocol for DSH Remote Control: sealed-record encryption (XSalsa20-Poly1305), key derivation, pairing URI, relay control frames, payload catalog. Pure functions, zero I/O. DSH 远控的线协议层：密封记录加密、KDF、配对 URI、控制帧与载荷目录，纯函数零 I/O。

Ecosystem pluginSecurityFile

Verification

L5 · Ecosystem plugin

Ecosystem plugin

Risk

LowRisk

Health

Active

Trust

Silver

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 doesAI

Pure-function wire protocol for DSH Remote Control: sealed-record encryption, key derivation, pairing URIs, relay control frames and payload catalog.

XSalsa20-Poly1305 sealed-record encryption, pure functions with zero I/O
Key derivation plus pairing URI generation for device pairing
Defines relay control frames and the payload catalog

securityAI

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 @dsh-remote/protocol@3.2.5

security scan passed · npm package v3.2.5

Install method: npm · 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

Declared DSH compatibilityfrom package.json · peerDependencies

author declared no dsh version requirement

○ The author declares no dsh version requirement — install is not blocked by version.

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

○ Ecosystem plugin

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.2 current	dsh 0.2.1-alpha.4	dsh 0.2.1-alpha.2
3.1.8	·	·	·
3.1.5	○	○	·
v3.1.5	·	·	○

Install compatibility (by plugin version, dsh versions within)

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

3.1.8npm2026-10-21

@dsh-remote/protocol

Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.

3.1.5npm○ 2 ecosystem plugin2026-10-18

@dsh-remote/protocol

○dsh 0.2.1-rc.2current2026-10-18Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: npm · @dsh-remote/protocol@3.1.5

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

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: protocol@3.1.5@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-18 · expires: 2026-10-25

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record protocol@3.1.8@dsh0.2.1-rc.2 (l3-fullscan)

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

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

L2 · Structured✓ Passed

↳ carried from earlier record protocol@3.1.8@dsh0.2.1-rc.2 (l3-fullscan)

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

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

L3 · Install spec✓ Passed

↳ carried from earlier record protocol@3.1.8@dsh0.2.1-rc.2 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec @dsh-remote/protocol · channel npm package · outcome ran · exit 0

check took: 10.6s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec @dsh-remote/protocol · channel npm package · outcome ran · exit 0

check took: 10.6s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec @dsh-remote/protocol · channel npm package · outcome ran · exit 0

check took: 10.6s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec @dsh-remote/protocol · install mode reused L4 scratch

check took: 91ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-18

ready line dsh web: http://127.0.0.1:59583/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-18

path / · HTTP 200 · took 91ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-18

verdict not-found · entries 149

phases: active 121 · null 28

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-16Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.4
• Plugin artifact: npm · @dsh-remote/protocol@3.1.5

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

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: protocol@3.1.5@dsh0.2.1-alpha.4 · profile: l4-sandbox

Issued: 2026-10-16 · expires: 2026-10-23

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record protocol@3.1.8@dsh0.2.1-rc.2 (l3-fullscan)

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

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

L2 · Structured✓ Passed

↳ carried from earlier record protocol@3.1.8@dsh0.2.1-rc.2 (l3-fullscan)

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

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

L3 · Install spec✓ Passed

↳ carried from earlier record protocol@3.1.8@dsh0.2.1-rc.2 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-16

spec @dsh-remote/protocol · channel npm package · outcome ran · exit 0

check took: 11.2s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-16

spec @dsh-remote/protocol · channel npm package · outcome ran · exit 0

check took: 11.2s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-16

spec @dsh-remote/protocol · channel npm package · outcome ran · exit 0

check took: 11.2s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-16

spec @dsh-remote/protocol · install mode reused L4 scratch

check took: 466ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-16

ready line dsh web: http://127.0.0.1:51207/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-16

path / · HTTP 200 · took 466ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-16

verdict not-found · entries 149

phases: active 121 · null 28

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.

v3.1.5github○ 1 ecosystem plugin2026-10-14

https://github.com/dsh-remote/protocol

○dsh 0.2.1-alpha.22026-10-14Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.2
• Plugin artifact: github · https://github.com/dsh-remote/protocol#v3.1.5

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

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: protocol@v3.1.5@dsh0.2.1-alpha.2 · profile: l4-sandbox

Issued: 2026-10-14 · expires: 2026-10-21

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record protocol@3.1.8@dsh0.2.1-rc.2 (l3-fullscan)

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

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

L2 · Structured✓ Passed

↳ carried from earlier record protocol@3.1.8@dsh0.2.1-rc.2 (l3-fullscan)

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

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

L3 · Install spec✓ Passed

↳ carried from earlier record protocol@3.1.8@dsh0.2.1-rc.2 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec github:dsh-remote/protocol#v3.1.5 · channel GitHub source · outcome ran · exit 0

check took: 19.8s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec github:dsh-remote/protocol#v3.1.5 · channel GitHub source · outcome ran · exit 0

check took: 19.8s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec github:dsh-remote/protocol#v3.1.5 · channel GitHub source · outcome ran · exit 0

check took: 19.8s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec github:dsh-remote/protocol#v3.1.5 · install mode reused L4 scratch

check took: 1.9s

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-14

ready line dsh web: http://127.0.0.1:55534/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-14

path / · HTTP 200 · took 1.9s

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-14

verdict not-found · entries 149

phases: active 121 · null 28

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:

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.

protocolAutomated review · daily

Static low, dynamic no conclusion — stricter wins → overall low.

static low→dynamic no conclusion→overall low

0 critical·0 high

lowoverall · low

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

Version binding

plugin versionv3.2.5

scanned version3.2.5npm2026-10-21

current version3.2.5same version

vet verdictclean · npm

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 (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.

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-21 · activity: Active

• Repo created: 2026-10-08

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/dsh-remote/protocol

Plugin notes

What is @dsh-remote/protocol?

@dsh-remote/protocol is an ecosystem plugin maintained by @dsh-remote: it installs via dsh plugin add but declares no dsh.bundle and mounts nothing — installing it adds no plugin capability; use the source repository directly. It is cataloged on dsh.so as a Security entry, with a public source repository and automated static security scan.

How do I install @dsh-remote/protocol?

This is an ecosystem plugin: it installs via dsh plugin add but declares no dsh.bundle and mounts nothing — installing one adds no plugin capability; use the source repository directly. Its level reads L5 · Ecosystem plugin; 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 (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, and its conclusion can only raise the combined verdict, never exempt it. 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-21

@dsh-remote/protocol

What it doesAI

Installation

Verification & Compatibility○ Ecosystem plugin

Author badges

Security Report

Activity

Source

Author README