Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
Installation
dsh plugin --profile web add github:krutziy/dsh-memory#v0.8.0security scan passed · source release v0.8.0
Install 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 | dsh 0.2.1-alpha.4 |
|---|---|---|
| v0.7.0 | · | · |
| v0.3.1 | ✓ | · |
v0.7.0github2026-10-21
https://github.com/krutziy/dsh-memory
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.3.1github✓ 1 runtime-verified2026-10-19
https://github.com/krutziy/dsh-memory
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/krutziy/dsh-memory#v0.3.1
ID: dsh-memory-47@v0.3.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-memory-47@v0.7.0@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-memory-47@v0.7.0@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-memory-47@v0.7.0@dsh0.2.1-rc.2 (l3-fullscan)
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-memory-47/)``[](https://www.dsh.so/artifact/dsh-memory-47/)`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 — stricter wins → overall medium.
v0.8.0dsh manifestv0.8.0git2026-10-21v0.8.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show 2 audit findings
- mediumAuto-recall re-injects stored memory as a user-role message, giving captured content a persistent instruction channel
index.jsCaptureController stores assistant answers and user text verbatim (only secret patterns are redacted) into Qdrant, and RecallController later appends them to a future turn's messages with role 'user'. Assistant text can be shaped by untrusted content the agent processed in an earlier session (web pages, tool/MCP output), so injected instructions survive the session boundary and are re-delivered as if the user had written them. The only mitigations are prose ('仅供参考；若与当前对话冲突，以当前对话为准') and the UI rendering the message as a context-injection row; nothing tags memory content provenance or neutralis
- lowRead-only memory endpoints (/status, /memories, /export) are registered without the CSRF header or any auth check
index.jsAll state-changing routes correctly require the custom x-dsh-memory header (trustedPost), but the three GET routes accept any request that can reach the DSH web server and return full conversation-derived memory text, including /export which dumps up to 20000 items. The plugin's own comment claims these routes are '仅本机可访问', which is enforced nowhere in the code; on a non-loopback binding, a reverse proxy, or via DNS rebinding, stored memory (facts, preferences, project details, partially redacted credentials) is readable without credentials.
Bundled host code is fully visible: no code execution or hidden exfiltration, but stored memory is re-injected into future turns as a user-role message and read-only memory endpoints skip the CSRF header check.
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-10-17
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/krutziy/dsh-memory
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).