Project-Memory-Agent

Project Memory gives coding agents a single, trustworthy memory for a software repository — so they stop re-learning the same facts and stop writing conflicting "memory" files.

PluginAI ModelsDeveloperKnowledgeContentMemory

Verification

L3 · Install spec

Failed

Risk

LowRisk

Health

Stable

Trust

Silver

Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.2 · last checked 10-21Install verification details →

What it doesAI

Provides coding agents with a single, trustworthy memory of a repository to avoid re-learning and conflicting memory files.

Single trusted memory for coding agents
Avoids re-learning repository facts
Eliminates conflicting memory files

aiAImemoryAI

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 @lovedolove/dsh-project-memory

verified

Install method: npm · sandbox install failed (L4)

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

Declared DSH compatibilityfrom package.json · peerDependencies

only dsh 0.1.2-rc.1 and up, below 0.2.0

Based on 1 requirement(s) across 2 @deepseek-ai/dsh-* packages.

raw ranges

>=0.1.2-rc.1 <0.2.0-0 ×2

✗ Running dsh 0.2.1-rc.2 is outside the declared range — the official install gate rejects it (incompatible-version).

To force-install, grant an exact-version exemption: dsh plugin allow-version project-memory-agent@0.5.4 0.2.1-rc.2 (the exemption lives in the local profile; this site does not assume one)

Whether it actually runs is a separate question → see the measured matrix below (L1–L5).

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.2	dsh 0.1.7-rc.2	dsh 0.1.6-alpha.2	dsh 0.1.6-alpha.1	dsh 0.1.5-rc.2
0.5.4	·	·	·	·	·

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

0.5.4npm2026-10-18

@lovedolove/dsh-project-memory

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

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:

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.

project-memory-agentAutomated review · daily

Static low; dynamic no conclusion (static stands) → overall low.

static low→dynamic no conclusion→overall low

vet findings0 critical·0 high

lowoverall · low

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin versionv0.5.4dsh manifest

scanned version0.5.4npm2026-10-25

current version0.5.4same version

vet verdictclean · npm

Vet is an AST static scan (npm artifact or git source).

show static findings (4)

warningfsWrite · filesbin/migrate-docs.mjs:89
fs.writeFileSync(filePath, updatedMarkdown, 'utf8');
warningshellExec · shellsrc/evidence/git-resolver.mjs:21
const res = execFileSync('git', ['rev-parse', '--is-inside-work-tree'], {
warningshellExec · shellsrc/evidence/git-resolver.mjs:41
execFileSync('git', ['rev-parse', '--verify', `${gitRef}^{commit}`], {
warningshellExec · shellsrc/evidence/git-resolver.mjs:67
const content = execFileSync('git', ['cat-file', '-p', `${gitRef}:${filePath}`], {

2dynamic auditmodel reads redacted source context · never executes plugin code

no dynamic conclusion (source harvest or model call failed) — no conclusion is not a pass; the overall rating falls back to the static tier.

Rule (2026-10-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. 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 static/vet.

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-09-22 · activity: Stable

• Repo created: 2026-08-27

• Stars: ★ 5 · Forks: 2

• Health: Stable — committed within 90 days

Source

GitHub: github.com/LoveDoLove/Project-Memory-Agent

Plugin notes

What is the Project-Memory-Agent DeepSeek Harness plugin?

Project-Memory-Agent is a DeepSeek Harness plugin maintained by @LoveDoLove. It is cataloged on dsh.so as a AI Models plugin for Memory tasks, with a public GitHub source, declared install command, and automated static scan results; plugins static-flagged at warn or above also carry a model-driven dynamic security audit record.

How do I install Project-Memory-Agent?

Run dsh plugin --profile web add @lovedolove/dsh-project-memory in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run 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 (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above; when it reaches a conclusion that conclusion is authoritative for the combined verdict — it may raise or lower it — and the static/vet fused verdict applies only when there is none. Exemptions stay manual: the audit never writes the suppression list. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-09-26