Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
DSH(DeepSeek Harness)插件:把一份基于文件的本地记忆档案(日记 / 状态 / 生长记录 / 事件流)搬进设置页面板 —— 概览、搜索、追加、谨慎编辑,读写都带指纹守卫与改前备份。MIT。
Installation
dsh plugin --profile web add github:S3K926/dsh-memory-board#v1.1.0Install 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 |
|---|---|
| v1.1.0 | ✓ |
v1.1.0github✓ 1 runtime-verified2026-10-18
https://github.com/S3K926/dsh-memory-board
✓dsh 0.2.1-rc.2current2026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/S3K926/dsh-memory-board#v1.1.0
ID: dsh-memory-board@v1.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-memory-board/)``[](https://www.dsh.so/artifact/dsh-memory-board/)`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.
v1.1.0dsh manifestv1.1.0git2026-10-21v1.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningfsWrite · files
lib/fs-guards.js:85fs.writeFileSync(temp, text, { encoding: 'utf8' }); - warningfsWrite · files
lib/fs-guards.js:115fs.writeFileSync(dest, toCrlf(text), { encoding: 'utf8' }); - warningfsWrite · files
lib/panel-state.js:98fs.writeFileSync(temp, text, { encoding: 'utf8' }); - warningchildProcess · code-exec
lib/sync.js:24const probe = spawnSync(candidate, ['--version'], { encoding: 'utf8', timeout: 10000, windowsHide: true }); - warningchildProcess · code-exec
lib/sync.js:59const result = spawnSync(python, syncArgv(script, apply), {
show 4 audit findings
- lowMutating /api/memory routes accept GET and rely only on a static confirm token, with no origin/token check
lib/router.js:345All state-changing routes (write unlock, diary append/delete, state edit/delete, growth append, init, sync/merge) are registered with methods ['GET','POST'] and parse params from the query string; the only write authorization beyond the host's own auth is the literal confirm=yes plus an ack equal to the target name. If the harness serves this fetch surface to browser contexts without origin/CSRF protection (not visible in this plugin), a cross-site simple GET could unlock the write switch (when config readOnly:false) and then append or delete archive content.
- lowBoot-task migration consumes and deletes another plugin's state file, then injects its content as a user-role message
lib/boot-tasks.js:86Content written to ~/.dsh/session-switch/boot-tasks.json (owned by the retired session-switch plugin) is read at startup, appended to the agent's next turn as a message with role:'user' (source.kind 'boot-tasks'), and then rmSync'ed. Anything that can write that path can shape the agent's instructions for one turn and destroys the other plugin's data. The normal task-file path has the same property but is authored by this agent itself.
- lowSync routes execute Python scripts whose content comes from the user-selected archive root
lib/sync.js:59The script name is hardcoded (SYNC_SCRIPTS) and no shell is used, but the script body is whatever sits in <root>/生长/<name>.py. If a user adopts or imports an archive from an untrusted source and then (writable config + unlocked switch + confirm=yes + ack) triggers /sync/merge, arbitrary Python from that archive runs with the user's privileges.
- lowindex.js imports ./lib/selftest.js which is absent from the audited/published file set
index.js:35Static ESM import of a module that does not exist in the harvested (and package.json 'files' declared) source set would throw ERR_MODULE_NOT_FOUND at load time, so the whole plugin including all 21 routes fails to load; it also means the --selftest path referenced throughout the comments is unverified.
Heuristic flags are refuted at runtime: writes are triple-gated and atomically verified, exec is a hardcoded whitelist without a shell; residual issues are low-severity hardening gaps.
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-21 · activity: Active
• Repo created: 2026-09-28
• Stars: ★ 17 · 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).
