Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Turns DeepSeek conversations into structured development requirements and hands them to the DSH Agent to execute.
- One-click: extracts goals, constraints and acceptance criteria from full chats
- Switchable enhancement service for long conversations (off, Jev, or self-hosted Laya)
- Lets you send open questions back to DeepSeek and continue long tasks in new sessions
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:TinyPandaGame/SpecsRelay-DSHInstall method: GitHub · runtime verified (L5)
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|
| c4aa97 | ✓ | ✓ | ✓ |
c4aa97github✓ 3 runtime-verified2026-10-19
https://github.com/TinyPandaGame/SpecsRelay-DSH
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/TinyPandaGame/SpecsRelay-DSH (version unstated)
ID: specsrelay-dsh-2@c4aa97@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: github · https://github.com/TinyPandaGame/SpecsRelay-DSH (version unstated)
ID: specsrelay-dsh-2@c4aa97@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-14L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/TinyPandaGame/SpecsRelay-DSH (version unstated)
ID: specsrelay-dsh-2@c4aa97@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/specsrelay-dsh-2/)``[](https://www.dsh.so/artifact/specsrelay-dsh-2/)`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 — stricter wins → overall medium.
v0.11.2dsh manifest0.11.2git2026-10-210.11.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningnetIp · network
index.js:432const pathname = new URL(req.url ?? "/", "http://127.0.0.1").pathname; - warningnetIp · network
index.js:1152"http://127.0.0.1" - warningnetIp · network
index.js:1187"http://127.0.0.1" - warningshellExec · shell
installer/hosts.js:36return execFileSync( - warningchildProcessImport · code-exec
installer/install.js:1import { spawn } from "node:child_process";
show 2 audit findings
- mediumWebUI routes trust any loopback peer; origin check is moot and DNS rebinding reaches conversation data and the DeepSeek panel
index.js:149isBrowserRequestAllowed short-circuits on the TCP peer address, and for a browser talking to 127.0.0.1 that address is always loopback, so the fallback origin/host comparison (parsed.host === host) never runs and could not stop DNS rebinding anyway since both headers are the attacker's hostname. Any page the user visits whose hostname resolves to 127.0.0.1, or any local process, can then GET /specsrelay/v1/handoffs and /specsrelay/v1/captures/latest (imported DeepSeek transcripts up to 400k chars), POST /specsrelay/v1/clarification/begin to type and send a message into the user's live chat.dee
- lowOpt-in enhancement path sends redacted conversation excerpts and a stored API key to a hardcoded third-party endpoint
lib/jev-router.js:250When the user enables the Jev router (env SPECSRELAY_JEV_ROUTER or the enhancement settings UI) or selects Laya, excerpts of the current DSH conversation / imported DeepSeek text (redacted via redactSecrets and truncated to 1600 chars by boundedStateText) plus a Bearer credential are POSTed to api.typesafe.ai or the user-entered Laya URL. This is intentional opt-in functionality and is bounded, but it is a real off-machine egress of user conversation content that should stay clearly disclosed; because enhancement settings are writable through the weakly protected HTTP route above, the selectio
Mostly well-bounded plugin, but WebUI routes authenticate on loopback address alone, so DNS rebinding can read imported conversations and drive the DeepSeek panel.
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-09-25 · activity: Active
• Repo created: 2026-08-15
• Stars: ★ 2 · 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).
