Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
Data as of (UTC)
What it does
DSH 多实例通讯底座：文件总线 + 在线名册 + 点对点/广播 + 收件箱 + 会话注入（多智能体工作台的 L0 层）
Installation
dsh plugin --profile web add github:jonah791/dsh-agent-clusterInstall method: GitHub · sandbox install failed (L4)
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 4 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×4
✗ Running dsh 0.2.1-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-agent-cluster@0.2.0 0.2.1-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.3 current | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| bcde4a | · | · | · | · | · |
| 941f63 | ✗ | ○ | ○ | ○ | ○ |
bcde4alocal2026-09-15
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
941f63github1 failed2026-10-26
https://github.com/jonah791/dsh-agent-cluster
✗dsh 0.2.1-rc.3current2026-10-26L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@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.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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-19not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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-18not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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-11not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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-09not tested
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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-30not tested
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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-26not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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.12026-09-24not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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.1.6-alpha.22026-09-20not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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-17not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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-15not tested
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-15 · expires: 2026-09-22
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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-04not tested
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-cluster (version unstated)
ID: dsh-agent-cluster@941f63@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
This level was not executed in this scan.
This level was not executed in this scan.
↳ carried from earlier record dsh-agent-cluster@bcde4a@dsh0.1.5-rc.2 (l3-fullscan)
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-agent-cluster/?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.
v0.2.00.2.0git2026-10-250.2.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningnetIp · network
scripts/join-demo.mjs:72hostBase = 'http://127.0.0.1:' + String(node.port) - warningnetIp · network
scripts/join-demo.mjs:82myBaseUrl: () => 'http://127.0.0.1:3999', - warningnetIp · network
scripts/join-demo.mjs:156member: { memberId: 'stranger-9', trust: 'known', capabilities: ['cluster'], endpoint: 'http://127.0.0.1:4100' }, - warningnetIp · network
scripts/peer-demo.mjs:48const url = 'http://127.0.0.1:' + String(node.port) + INBOX_PATH - warningnetIp · network
scripts/peer-demo.mjs:83const ping = await fetch('http://127.0.0.1:' + String(node.port) + PING_PATH) - warningnetIp · network
src/join.ts:97const loopback = base.startsWith('http://127.0.0.1') || base.startsWith('http://localhost')
show 3 audit findings
- highInvite tokens are self-certifying: a forged token enrols an arbitrary member with an attacker-chosen secret
src/join.ts:134handleJoin accepts any token whose 64-bit fingerprint is internally consistent. The fingerprint is explicitly 'not authentication' (src/invite.ts:14-16: 'The fingerprint only detects mangling, it is not authentication. Whoever holds the token also holds the secret, so they could re-mint the fingerprint.'), and the host never checks the token against a mint log, nonce issue log, or a MAC. decideJoin only compares net (which every distributed token reveals), exp, member==claimant.memberId and nonce-seen. Therefore anyone who can reach the join endpoint and knows the network name can build a toke
- mediumUnsanitised self-reported member id is used to name the persisted member record (path traversal)
src/join.ts:146For open tokens (member '*') the member id comes straight from the untrusted request body; parseMemberRecord (src/transport.ts) only requires 'typeof o.memberId === 'string' && o.memberId !== ''', and invite.ts isSafeField allows '/' and '.'. The documented member store shape is one file per member named '<memberId>.json' (src/join.ts:33 '写成员记录'; scripts/join-demo.mjs makeStore uses writeFileSync(join(dir, rec.memberId + '.json')) and is described as '与线上同一形状'). An id such as '../members/host-0' or '../../evil' therefore writes/overwrites JSON at a path outside the members directory, letting a
- mediumUnauthenticated join response returns the host's full self member record, which may carry its secret
src/join.ts:168JoinDeps.selfRecord is typed as MemberRecord, whose shape (src/transport.ts) includes an optional 'secret' field — and the client side deliberately overrides it ('const mine: MemberRecord = { ...hostRec, trust: 'known', secret: inv.secret, ... }'), confirming the host record may indeed carry a secret. handleJoin is unauthenticated by design and, combined with the forged-token issue above, is reachable by any network caller: the full host member record (id, endpoint, capabilities, possibly the host's own signing secret and notes) is echoed back in the response body. If selfRecord includes a sec
Self-certifying invite tokens let anyone who can reach the unauthenticated join endpoint and knows the network name enrol as a trusted member; unsanitised member ids also name member files.
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-10-15 · activity: Active
• Repo created: 2026-09-14
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 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-agent-cluster?
dsh-agent-cluster 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-agent-cluster?
Run dsh plugin --profile web add github:jonah791/dsh-agent-cluster in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest, but its install spec is not verified yet (L3); sandbox install and runtime testing have not passed.
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-10-26 (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.