Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
A creative branching canvas plugin for DeepSeek Harness, organizing AI-generated ideas into a tree workspace for viewing, comparing, and forking.
- Tree-structured canvas for branching creative ideas
- View, compare, and fork AI-generated proposals in DSH
- Native input to set requirements and proposal count
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-plugin-ramifyInstall method: npm · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.2-rc.3
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.
6 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-09 · 6 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-23 → 10-19 · 4 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
10-03 → 11-17 · 43 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
10-03 → 11-18 · 44 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.2-alpha.2 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 |
|---|---|---|---|---|---|
| 0.1.0 | ✗ | ✗ | ✗ | ✗ | ✗ |
0.1.0npm9 failed2026-11-16
dsh-plugin-ramify
✗dsh 0.2.2-rc.32026-11-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-plugin-ramify@0.1.0
ID: ramify-dsh@0.1.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-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.2-rc.12026-11-04L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-plugin-ramify@0.1.0
ID: ramify-dsh@0.1.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.2-alpha.22026-11-04L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-alpha.2
- • Plugin artifact: npm · dsh-plugin-ramify@0.1.0
ID: ramify-dsh@0.1.0@dsh0.2.2-alpha.2 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
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.52026-10-30L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-plugin-ramify@0.1.0
ID: ramify-dsh@0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
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 · dsh-plugin-ramify@0.1.0
ID: ramify-dsh@0.1.0@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-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-plugin-ramify@0.1.0
ID: ramify-dsh@0.1.0@dsh0.2.1-rc.2 · 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.42026-10-15L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-plugin-ramify@0.1.0
ID: ramify-dsh@0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
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-10L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-plugin-ramify@0.1.0
ID: ramify-dsh@0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
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-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-plugin-ramify@0.1.0
ID: ramify-dsh@0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
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/ramify-dsh/?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 medium (authoritative when present) → overall medium.
v0.1.0dsh manifest0.1.0npm2026-11-190.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningnetIp · network
lib/client.js:97var RAMIFY_URL = "http://127.0.0.1:9531/"; - warningnetIp · network
lib/client.js:130ramifyWorkspaceFrame()?.postMessage({ type: "ramify:dsh-preferences", version: 1, ...preferences }, "http://127.0.0.1:9531"); - warningnetIp · network
lib/client.js:151if (event.origin !== "http://127.0.0.1:9531" || event.source !== ramifyWorkspaceFrame()) return; - warningchildProcess · code-exec
lib/index.js:117const child = spawn(process.execPath, [serverEntry], { - warningnetIp · network
lib/index.js:54this.url = `http://127.0.0.1:${config.port}`;
show 3 audit findings
- mediumBundled canvas runtime is spawned with HOST=0.0.0.0, exposing a loopback-only API to the LAN
lib/index.js:121Every URL, health check, postMessage targetOrigin and origin check in this plugin assumes 127.0.0.1:9531, yet the child process is told to bind all interfaces. If app/dist/server.mjs honors HOST (it is not part of the reviewed source), any host on the same network can reach the unauthenticated project/node/artifact API, read creative prompts and stored content, and inject or overwrite artifacts. Apply() awaits runtime.start() on plugin load, so the service is active whenever the plugin is installed.
- mediumAny local process answering /api/health as ramify is reused and receives all project data
lib/index.js:170startOnce() treats an existing listener as the Ramify backend as soon as health returns service === "ramify" (reuse path lines 107-111), without verifying instanceId or ownership; the instanceId check exists only for the instance this plugin spawned. A local process that binds 127.0.0.1:9531 before the plugin loads becomes the API: every ramify_* tool sends user prompts, node titles/content and artifacts there, and its responses are fed back to the model. Because the client trusts origin http://127.0.0.1:9531, that page is also the accepted source for ramify:dsh-submit messages, which are auto
- lowCanvas messages auto-submit agent prompts without user confirmation
lib/client.js:295Any script executing in the embedded canvas window can send ramify:dsh-submit, and the host immediately submits a generated prompt (including request.prompt and nodeTitle text) to the agent, which then acts with the user's tool permissions. Origin and source are validated at line 292, so unrelated pages are blocked; the residual risk is content executed inside the canvas itself. ramify_node_complete explicitly accepts artifacts that "may contain executable markup" and the iframe has no sandbox attribute, so whether artifact scripts can reach the canvas window identity depends on the unreviewed
Local canvas is spawned on 0.0.0.0, any process squatting port 9531 is trusted, and canvas messages auto-submit prompts to the agent; no remote egress found.
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-01 · activity: Stable
• Repo created: 2026-08-13
• Stars: ★ 21 · 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 ramify-dsh?
ramify-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 ramify-dsh?
Run dsh plugin --profile web add dsh-plugin-ramify 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-19 (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.
