Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Project-level persistent memory plugin for deepseek-harness with auditable Markdown memory files and lifecycle tools.
- Zero-dependency installable via dsh
- Auditable Markdown memory files
- Memory tools: load_context, upsert, finalize, forget
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 github:JasperGuWP/dsh-project-memoryInstall method: GitHub · runtime verified (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.
7 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-05 · 7 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
10-06 → 11-05 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
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
Only 0 points (< 3): no chart yet
no data yet
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.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| fe236c | · | ✓ | ✓ | ✓ | ✓ |
| 2925eb | ✓ | ○ | · | · | · |
fe236cgithub✓ 18 runtime-verified◐ 1 testing2026-11-14
https://github.com/JasperGuWP/dsh-project-memory
✓dsh 0.2.2-rc.12026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
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.2.1-rc.52026-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-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.
✓dsh 0.2.1-rc.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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.2.1-alpha.42026-10-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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.2.1-alpha.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.2.0-rc.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.2.0-rc.1 · profile: l4-sandbox
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.
✓dsh 0.1.7-rc.22026-09-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
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-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
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.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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.3-alpha.22026-09-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
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.3-alpha.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.2-rc.12026-09-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory#fe236c
ID: dsh-project-memory-2@fe236c@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
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.2-alpha.12026-09-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dsh0.1.2-alpha.1 · profile: l3-fullscan
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
active in loader tree (149 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◐dsh 0.1.1-rc.22026-08-28L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.1.1-rc.2
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory#fe236c
ID: dsh-project-memory-2@fe236c@dsh0.1.1-rc.2 · profile: l3-fullscan
Issued: 2026-08-28 · expires: 2026-09-04
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory (version unstated)
ID: dsh-project-memory-2@fe236c@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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.
2925ebgithub✓ 1 runtime-verified2026-11-16
https://github.com/JasperGuWP/dsh-project-memory
✓dsh 0.2.2-rc.32026-11-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory#2925ebfca3cc31764c4cbffe8ef8beafe3660cc0
ID: dsh-project-memory-2@2925ebfca3cc31764c4cbffe8ef8beafe3660cc0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
active in loader tree (206 entries)
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-12not tested
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/JasperGuWP/dsh-project-memory#2925ebfca3cc31764c4cbffe8ef8beafe3660cc0
ID: dsh-project-memory-2@2925ebfca3cc31764c4cbffe8ef8beafe3660cc0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-12 · expires: 2026-11-19
View checks & evidence
inventory probe failed (rpc-error) — inconclusive, not a plugin verdict (reinterpreted 2026-11-17)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-project-memory-2/?ref=badge)``[](https://www.dsh.so/artifact/dsh-project-memory-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-project-memory-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-project-memory-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-project-memory-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-project-memory-2/?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.0dsh manifest0.1.0git2026-11-190.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningfsWrite · files
memory-plugin.js:281await fs.writeFile(indexPath, `${lines.join('\n')}\n`, 'utf8'); - warningfsWrite · files
memory-plugin.js:307await fs.writeFile(indexPath, kept.length > 0 ? `${kept.join('\n')}\n` : '', 'utf8'); - warningfsWrite · files
memory-plugin.js:680await fs.writeFile(join(resolved.memoryRoot, file), body, 'utf8'); - warningfsWrite · files
memory-plugin.ts:383await fs.writeFile(indexPath, `${lines.join('\n')}\n`, 'utf8') - warningfsWrite · files
memory-plugin.ts:406await fs.writeFile(indexPath, kept.length > 0 ? `${kept.join('\n')}\n` : '', 'utf8') - warningfsWrite · files
memory-plugin.ts:790await fs.writeFile(join(resolved.memoryRoot, file), body, 'utf8')
show 5 audit findings
- mediumStored memory is replayed into the model context as authoritative guidance (persistent prompt injection)
memory-plugin.js:452Any text written to memory/*.md (by the model via memory_upsert, by the user, or by anyone able to place files in the project tree) is later returned verbatim by memory_load_context and the system prompt instructs the model to follow it. A malicious repo or a crafted 'remember this' request can therefore plant instructions that persist across sessions and are treated as project conventions; only secrets are filtered, not directives.
- mediummemory_read follows symlinks: a .md symlink in memory/ can pull files from outside the workspace into model context
memory-plugin.js:559isSafeFile only validates the file NAME (no separators, ends with .md, no leading dot). fs.readFile and fs.readFile(indexPath) follow symlinks, so a memory/<name>.md symlink pointing to e.g. ~/.aws/credentials, combined with a matching line in MEMORY.md, causes out-of-workspace content to be scored and returned in the snippet field. Reads are not passed through detectSensitive, so secret material in the target is not filtered before reaching the model.
- lowProtected index/reference filenames compared case-sensitively, unsafe on case-insensitive filesystems
memory-plugin.js:817The guard in memory_forget compares exact strings and the filename check only requires ending in .md, so target 'memory.md' passes on macOS/Windows where it resolves to the same file as MEMORY.md; fs.unlink then destroys the index. Symmetrically, slugifyFile('Memory') produces 'memory.md', so an upsert can overwrite the index on those filesystems.
- lowIndex line built from raw topic/summary allows newline injection into MEMORY.md
memory-plugin.js:160validateArgs only enforces the string type, so topic/summary/category may contain newlines. A crafted topic such as 'x\n- [convention] rules:run this → foo.md' inserts a syntactically valid extra index row that later parses via INDEX_LINE_RE and is returned to the model as a genuine catalog/matched memory.
- lowFalls back to process.cwd() when sandboxPolicy is absent, writing memory outside the session workspace
memory-plugin.js:411sandboxPolicy is retrieved with ctx.get() and is not declared in inject, so its absence is a supported state. In that case every memory read/write resolves to the harness process CWD (an install/host directory shared by all sessions of that process), so memories written by one session become visible to, or overwrite, another's.
Local Markdown memory plugin with no shell/network/deps and solid path-traversal guards, but stored memory is replayed to the model as guidance and symlinks/fallbacks widen file scope.
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-08-19 · activity: Inactive
• Repo created: 2026-08-19
• Stars: ★ 1 · Forks: 0
• Health: Inactive — no commit in 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 dsh-project-memory?
dsh-project-memory 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-project-memory?
Run dsh plugin --profile web add github:JasperGuWP/dsh-project-memory in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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.
