Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Local HMAC-authenticated message broker for multi-agent collaboration between dsh, Codex, Claude Code & Hermes.
- HMAC-authenticated loopback relay
- Supports dsh, Codex, Claude Code, Hermes
- Wire protocol for agent collaboration
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-agent-relayInstall method: npm · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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-12) · 8 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-09 · 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
09-24 → 11-09 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-17 → 11-11 · 73 points
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
08-17 → 11-14 · 74 points
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 1 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×1
✗ Running dsh 0.2.2-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-relay@0.5.0 0.2.2-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.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 0.5.0 | · | · | ✓ | ✓ | ✓ |
0.5.0npm✓ 14 runtime-verified2026-11-14
dsh-agent-relay
✓dsh 0.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
active in loader tree (150 entries)
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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
active in loader tree (150 entries)
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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
active in loader tree (150 entries)
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
active in loader tree (150 entries)
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-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
active in loader tree (150 entries)
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-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
active in loader tree (150 entries)
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-24L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
active in loader tree (150 entries)
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
active in loader tree (150 entries)
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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
active in loader tree (150 entries)
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-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
View checks & evidence
active in loader tree (150 entries)
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
active in loader tree (150 entries)
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-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.2-rc.12026-09-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-agent-relay@0.5.0
ID: dsh-agent-relay@0.5.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
active in loader tree (150 entries)
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-agent-relay/?ref=badge)``[](https://www.dsh.so/artifact/dsh-agent-relay/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-relay/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-relay/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-relay/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-relay/?ref=badge-install)`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.5.0dsh manifest0.5.0npm2026-11-140.5.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningchildProcess · code-exec
adapters/backends/claude-backend.mjs:44const child = spawn(RESOLVED.file, [...RESOLVED.args, ...buildArgs(cwd)], { cwd, stdio: ['pipe', 'pipe', 'pipe'] }) - warningchildProcess · code-exec
adapters/backends/codex-backend.mjs:48const child = spawn(RESOLVED.file, [...RESOLVED.args, ...buildArgs(cwd)], { env, stdio: ['pipe', 'pipe', 'pipe'] }) - warningnetIp · network
adapters/hermes/example_hermes_plugin.py:25RELAY_BROKER_URL = __import__("os").environ.get("RELAY_BROKER_URL", "http://127.0.0.1:19121") - warningshellExec · shell
lib/memory-bridge.js:26const child = execFile( - warningshellExec · shell
lib/workspace.js:16return execFileSync('git', ['-C', root, ...args], { encoding: 'utf8', stdio: ['ignore', 'pipe', 'ignore'] }).trim() - warningnetIp · network
setup/selfcheck.js:46const brokerUrl = process.env.DSH_RELAY_BROKER_URL ?? 'http://127.0.0.1:19121'
show 3 audit findings
- mediumWrite-mode relay isolation silently falls back to the live workspace when the git tree is dirty
lib/workspace.js:41A write-mode relay request then executes directly in the agent's primary working directory. The only remaining protection is the lock in lib/lease.js, which serializes relay writers against each other but not against the human, the IDE, or the host agent editing the same tree. A dirty tree is the normal state during active development, so the module's own guarantee that 'the primary workspace is never modified' does not hold on the most common path for peer-controlled prompts, and the caller is not told the isolation was downgraded.
- mediumCodex backend disables approval and enforces no read-only sandbox when CODEX_SANDBOX is unset
adapters/backends/codex-backend.mjs:33The relay message body is piped to `codex exec` as the prompt with approval prompts disabled whenever CODEX_SANDBOX is not configured (the default). Unlike claude-backend.mjs, which hard-codes '--permission-mode plan', nothing in this file enforces a read-only sandbox on read/continue turns; the guarantee rests entirely on an optional environment variable and on Codex's own defaults. A peer that holds the shared broker secret can therefore send a message whose text instructs the model to act, and tool/shell execution happens in the relay cwd - which for read turns is the live workspace. The in
- lowModel-influenced memory query is appended to argv without a '--' terminator and its output is injected verbatim into peer context
lib/memory-bridge.js:28No shell is involved and `prog` is fixed by UNIFIED_MEMORY_CMD, so this is not command injection. However the query is derived from relay/model input and is placed after the 'search' subcommand without a '--' separator, so a query beginning with '-' is parsed as options of the memory CLI. The returned stdout is then embedded verbatim into another agent's request context by formatMemoryContext, giving peer-influenced text a direct path into a second agent's prompt.
Write-mode relay "isolation" degrades to the live workspace on a dirty git tree, and the Codex backend leaves its read-only sandbox to an optional env var.
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-13 · activity: Stable
• Repo created: 2026-08-14
• Stars: ★ 4 · Forks: 1
• Health: Stable — committed within 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-agent-relay?
dsh-agent-relay 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-relay?
Run dsh plugin --profile web add dsh-agent-relay in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.
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.