Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
DeepSeek Harness plugin letting an AI agent drive the Xiaohe Canvas to create e-commerce images, videos, audio and copy.
- Canvas agent creates, edits and deletes nodes, links and layouts
- Searches and applies e-commerce templates across 16 categories
- Generates images, videos, audio and copy; manages asset library
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.
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); the npm pair from every snapshot.
4 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-24 → 10-19 · 4 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-02 → 10-19 · 3 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-21 → 10-30 · 38 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-21 → 10-30 · 38 points
Installation
dsh plugin --profile web add xiaohe-canvas-dshInstall method: npm · 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
Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages. raw ranges
* ×1
✓ Running dsh 0.2.1-rc.5 is within the declared range — install is not blocked by version.
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 current | 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.1.3 | ✗ | ✗ | ✗ | ✗ | ✗ |
| 0.1.2 | · | · | · | · | · |
| 0.1.1 | · | · | · | · | · |
| 0.1.0 | · | · | · | · | · |
0.1.3npm6 failed2026-10-31
xiaohe-canvas-dsh
✗dsh 0.2.1-rc.5current2026-10-31L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · xiaohe-canvas-dsh@0.1.3
ID: xiaohe-canvas-dsh@0.1.3@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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-rc.32026-10-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · xiaohe-canvas-dsh@0.1.3
ID: xiaohe-canvas-dsh@0.1.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · xiaohe-canvas-dsh@0.1.3
ID: xiaohe-canvas-dsh@0.1.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · xiaohe-canvas-dsh@0.1.3
ID: xiaohe-canvas-dsh@0.1.3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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-12L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · xiaohe-canvas-dsh@0.1.3
ID: xiaohe-canvas-dsh@0.1.3@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · xiaohe-canvas-dsh@0.1.3
ID: xiaohe-canvas-dsh@0.1.3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.2npm✓ 3 runtime-verified2026-09-30
xiaohe-canvas-dsh
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · xiaohe-canvas-dsh@0.1.2
ID: xiaohe-canvas-dsh@0.1.2@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 · xiaohe-canvas-dsh@0.1.2
ID: xiaohe-canvas-dsh@0.1.2@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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · xiaohe-canvas-dsh@0.1.2
ID: xiaohe-canvas-dsh@0.1.2@dshunknown · profile: l3-fullscan
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.
0.1.1npm2026-09-20
xiaohe-canvas-dsh
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.1.0npm✓ 1 runtime-verified2026-09-18
xiaohe-canvas-dsh
✓dsh 0.1.6-alpha.22026-09-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · xiaohe-canvas-dsh@0.1.0
ID: xiaohe-canvas-dsh@0.1.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-18 · expires: 2026-09-25
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/xiaohe-canvas-dsh/?ref=badge)``[](https://www.dsh.so/artifact/xiaohe-canvas-dsh/?ref=badge-install)``[](https://www.dsh.so/artifact/xiaohe-canvas-dsh/?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.1.3dsh manifest0.1.3npm2026-11-010.1.3same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalshellExec · shell
lib/index.js:36execSync(`where ${cmd}`, { stdio: 'ignore' }); - criticalshellExec · shell
lib/index.js:39execSync(`which ${cmd}`, { stdio: 'ignore' }); - warningchildProcess · code-exec
lib/index.js:162canvasAgentProcess = spawn(cmd, finalArgs, { - warningnetIp · network
lib/index.js:27apiUrl: 'http://127.0.0.1:17371',
show 4 audit findings
- mediumDSH_TOKEN is passed on the child-process command line and echoed into the plugin log
lib/index.js:160The harness token taken from process.env.DSH_TOKEN is appended to the argv of a spawned process (readable via ps/tasklist by other local users and visible in process-monitoring tooling) and is also printed verbatim to stdout, so it can end up in terminal scrollback, DSH session transcripts and shared support logs. The same argv is handed to the third-party package launched through npx.
- mediumPlugin auto-downloads and executes an unpinned npm package via `npx -y` at load time
lib/index.js:124Because autoStartAgent defaults to true (lib/index.js:29), merely enabling the plugin causes npx to fetch the latest published version of @xiaohe-store/canvas-agent (and its dependency tree) from the public registry and execute it with the user's privileges, without version pinning or user confirmation. A compromised or hijacked upstream package/release turns this into silent remote code execution on the user machine.
- lowWindows spawn uses `shell: true` with concatenated arguments
lib/index.js:162On Windows the argv (including the DSH token) is joined into a cmd.exe command line, so any shell metacharacter in an argument would be interpreted by the shell. The arguments used today come from a fixed literal list plus a harness-issued token, so no attacker-controlled string was identified in the reached path; this is a hardening gap rather than a demonstrated injection.
- lowCanvas connect token placed in the URL query string
lib/index.js:254The token read from ~/.infinite-canvas/canvas-agent.json travels in the request URL, which is more likely to be captured by proxy/debug/access logging than a header. The default endpoint is loopback, so exploitation requires a modified apiUrl or local logging, keeping this at low severity.
Read-only-ish DSH bridge to a local Canvas Agent; real issues are the DSH_TOKEN leaking into process args/logs, unpinned npx auto-execution, and a loose Windows shell spawn.
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-02 · activity: Stable
• Repo created: 2026-09-17
• Stars: ★ 0 · Forks: 0
• 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 @wild-River2016/xiaohe-canvas-dsh?
@wild-River2016/xiaohe-canvas-dsh 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 @wild-River2016/xiaohe-canvas-dsh?
Run dsh plugin --profile web add xiaohe-canvas-dsh in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed 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-01 (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.