DeepSeek Harness plugin: multi-user English vocabulary bank - copy text, pick the user in a popup at the mouse position, LLM translation, SQLite counting, plus printable cards and a quiz loop. 自研 DSH 插件：多用户英语生词库（复制后在鼠标处弹窗点选入库 / LLM 翻译 / SQLite 计次 / 可打印记忆卡与考试闭环）
Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Multi-user English vocabulary bank: copy text, pick a user in a mouse-position popup, get LLM translations, SQLite counts, printable cards and quizzes.
- Copy text and pick the user in a popup at the mouse position
- LLM translation with SQLite-based occurrence counting
- Printable memory cards plus a quiz/exam loop
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-word-vaultInstall method: npm · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.1-rc.3
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 2 @deepseek-ai/dsh-* packages. raw ranges
>=0.1.1-rc.2 <0.2.0-0 || >=0.2.0-rc.1 <0.3.0-0 ×2
✓ 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.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| 1.11.0 | ✗ | ✗ | ✗ | · | · |
| 1.10.0 | · | · | · | ✗ | ✗ |
| 1.0.8 | · | · | · | · | · |
| 1.0.7 | · | · | · | · | · |
| 1.0.5 | · | · | · | · | · |
1.11.0npm3 failed2026-10-30
dsh-word-vault
✗dsh 0.2.1-rc.32026-10-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-word-vault@1.11.0
ID: dsh-word-vault@1.11.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
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 · dsh-word-vault@1.11.0
ID: dsh-word-vault@1.11.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
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 · dsh-word-vault@1.11.0
ID: dsh-word-vault@1.11.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
1.10.0npm2 failed2026-10-15
dsh-word-vault
✗dsh 0.2.1-alpha.22026-10-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-word-vault@1.10.0
ID: dsh-word-vault@1.10.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
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-word-vault@1.10.0
ID: dsh-word-vault@1.10.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
1.0.8npm1 failed2026-10-05
dsh-word-vault
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-word-vault@1.0.8
ID: dsh-word-vault@1.0.8@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
1.0.7npm1 failed2026-10-04
dsh-word-vault
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-word-vault@1.0.7
ID: dsh-word-vault@1.0.7@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
1.0.5npm1 failed2026-10-03
dsh-word-vault
✗prehistory2026-10-03L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-word-vault@1.0.5
ID: dsh-word-vault@1.0.5@dshunknown · profile: l4-sandbox
Issued: 2026-10-03 · expires: 2026-10-10
View checks & evidence
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-word-vault@1.11.0@dsh0.2.1-rc.5 (l3-fullscan)
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-word-vault/?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.
v1.11.0dsh manifest1.11.0npm2026-10-301.11.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningchildProcess · code-exec
capture.mjs:122this.child = spawn( - warningchildProcess · code-exec
cards.mjs:444child = spawn(cmd, args, { stdio: ["ignore", "ignore", "pipe"], windowsHide: true }); - warningnetIp · network
client.js:70unavailable: "配置面板不可用(设置服务未挂载)。可改用 http://127.0.0.1:3080/word-vault/settings", - warningnetIp · network
exam.mjs:272const url = new URL(req.url || "/", "http://127.0.0.1"); - warningnetIp · network
exam.mjs:350const origin = `http://127.0.0.1:${server.address() && server.address().port ? server.address().port : 0}`; - warningnetIp · network
exam.mjs:452url: `http://127.0.0.1:${port}/e/${token}`, - warningchildProcess · code-exec
photos.mjs:86child = spawn(cmd, args, { stdio: ["ignore", "pipe", "pipe"], windowsHide: true }); - warningchildProcess · code-exec
tts.mjs:61child = spawn(POWERSHELL, args, { stdio: ["ignore", "pipe", "pipe"], windowsHide: true });
show 1 audit findings
- mediumExam page embeds DB text into inline <script> via JSON.stringify, allowing </script> breakout
exam.mjs:41JSON.stringify does not escape '<' or '</script>'. The sentence/word/options are stored from captured clipboard context (extractSentenceFromContext over recorded text). A captured sentence containing '</script><script>...</script>' terminates the inline script and injects arbitrary JavaScript that runs in the local exam page origin (127.0.0.1:port), which holds the session token and can call /answer, /finish, /summary, /review-cards and /tts, and can exfiltrate to a remote host. Requires the victim to capture attacker-influenced text and generate an exam containing that word.
Vocabulary plugin spawns only fixed-arg PowerShell/browser processes, but the local exam page embeds DB text into a <script> via JSON.stringify, allowing script breakout from captured clipboard text.
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-15 · activity: Active
• Repo created: 2026-09-16
• Stars: ★ 1 · 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).
Frequently asked questions
What is dsh-word-vault?
dsh-word-vault 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-word-vault?
Run dsh plugin --profile web add dsh-word-vault 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-10-30 (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.