Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Lets Codex delegate tasks to the DSH desktop agent, showing sessions in the workspace, reusing context, and calling back on completion.
- Codex assigns tasks; DSH desktop carries them out in visible sessions
- Reuses saved session bindings to continue the same conversation
- Completion callback notifies the originating Codex chat for review
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:ericlee041769-hash/dsh-waibao#v0.1.0Install method: GitHub · sandbox install ok, web smoke failed (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 |
|---|---|---|---|
| v0.1.0 | ✗ | ✗ | ✗ |
v0.1.0github3 failed2026-10-20
https://github.com/ericlee041769-hash/dsh-waibao
✗dsh 0.2.1-rc.2current2026-10-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/ericlee041769-hash/dsh-waibao#v0.1.0
ID: dsh-waibao@v0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
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-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/ericlee041769-hash/dsh-waibao#v0.1.0
ID: dsh-waibao@v0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
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-13L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/ericlee041769-hash/dsh-waibao#v0.1.0
ID: dsh-waibao@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-13 · expires: 2026-10-20
View checks & evidence
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/dsh-waibao/)`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 low — stricter wins → overall low.
v0.1.0dsh manifestv0.1.0git2026-10-21v0.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningfsWrite · files
bin/cli.mjs:45fs.writeFileSync(temporary, JSON.stringify(binding, null, 2) + '\n'); - warningfsWrite · files
bin/install-skill.mjs:11await fs.writeFile(path.join(destination, 'SKILL.md'), template.replaceAll('__PACKAGE_ROOT__', root.replaceAll('\\', '/')).replaceAll('__NOD - warningchildProcess · code-exec
bin/job.mjs:28const child = spawn(job.connection.node, [job.connection.server], { - warningchildProcess · code-exec
bin/job.mjs:190const child = spawn(job.command.executable, job.command.args, { - warningfsWrite · files
bin/job.mjs:18fs.writeFileSync(temporary, JSON.stringify(job, null, 2) + '\n'); - warningfsWrite · files
bin/job.mjs:172fs.writeFileSync(record, JSON.stringify(job, null, 2) + '\n', { flag: 'wx', mode: 0o600 }); - warningfsWrite · files
bin/job.mjs:203fs.writeFileSync(job.exitPath, `${outcome.code ?? 'unknown'}\n`, { flag: 'wx' }); - warningfsWrite · files
src/host.mjs:140await fs.writeFile(connectionFile, JSON.stringify({pipe, token, pid: process.pid, startedAt: new Date().toISOString()}) + '\n', {mode: 0o600
show 2 audit findings
- lowDelegated task inherits full parent environment, including any secrets
bin/job.mjs:193The executable named in the user/skill-authored spec runs with every env var of the caller (API keys, tokens, cloud creds). If a spec or workspace is influenced by untrusted content, that process can read and exfiltrate those secrets.
- low0o600 on connection file is a no-op on Windows, the only supported platform
src/host.mjs:140The auth token gating the named pipe is written to disk with a POSIX mode that Node ignores on Windows; protection depends solely on the inherited directory ACL of the data dir. A loosened ACL on that directory would let another local user read the token and drive the authenticated pipe.
Token-authenticated local Windows named-pipe bridge with strict path validation; no eval or remote network. Only low hardening gaps: delegated task inherits full env, 0o600 ignored on Windows.
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-13 · activity: Active
• Repo created: 2026-10-13
• Stars: ★ 0 · 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).
