memory-eternal

🧠 给 AI 装第二大脑 · DSH 插件：对话结束自动沉淀知识卡，跨会话召回，知识图谱可视化，审核/回收/备份一体（SQLite，零外部依赖）

PluginKnowledgeStorageMemoryFileDatabase

Verification

L4 · Install tested

Failed

Risk

LowRisk

Health

Active

Trust

Silver

Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked 10-18Install verification details →

What it doesAI

Automatically condenses conversation-end knowledge into a local Markdown Vault with dedup, CJK search, and knowledge graph for agent recall.

Auto-saves knowledge cards to local Markdown Vault
Custom dedup and CJK search built in
Knowledge graph with review and recycle centers

knowledgeAImemoryAIfileAI

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 memory-eternal

verified 0.10.39

Install method: npm · sandbox install ok, web smoke failed (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

Declared DSH compatibilityfrom package.json · peerDependenciesdeclared in 0.10.26

only dsh 0.1.0-rc.2 and up, below 0.3.0

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

raw ranges

>=0.1.0-rc.2 <0.3.0-0 ×2

✓ Running dsh 0.2.1-rc.2 is within the declared range — install is not blocked by version.

Footnote: the author also wrote engines.dsh = ">=0.1.5-alpha.2 <0.3.0-0" — DSH does not read that field (not part of the verdict).

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 current	dsh 0.2.1-alpha.4	dsh 0.2.1-alpha.2	dsh 0.2.0-rc.2	dsh 0.2.0-rc.1
0.10.54	·	·	·	·	·
0.10.39	✗	·	·	·	·
0.10.38	·	·	·	·	·
0.10.31	·	·	·	·	·
0.10.29	·	✗	·	·	·

Install compatibility (by plugin version, dsh versions within)

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

0.10.54npm2026-10-21

memory-eternal

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

0.10.39npm1 failed2026-10-18

memory-eternal

✗dsh 0.2.1-rc.2current2026-10-18L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: npm · memory-eternal@0.10.39

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Failed

Sandbox install failed

L5 · failed

ID: memory-eternal@0.10.39@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-18 · expires: 2026-10-25

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-21

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-21

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec memory-eternal · channel npm package · outcome ran · exit 0

check took: 4.4s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec memory-eternal · channel npm package · outcome ran · exit 0

check took: 4.4s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec memory-eternal · channel npm package · outcome ran · exit 0

check took: 4.4s

L5 · Run tested✕ Failed

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec memory-eternal · install mode reused L4 scratch

check took: 0ms

Web boot readyL5.2_WEB_BOOT_READY✕ Failed

plugin tree failed to load

HTTP endpoint servedL5.3_HTTP_SERVED✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

0.10.38npm2026-10-18

memory-eternal

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

0.10.31npm2026-10-15

memory-eternal

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

0.10.29npm1 failed2026-10-15

memory-eternal

✗dsh 0.2.1-alpha.42026-10-15L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.4
• Plugin artifact: npm · memory-eternal@0.10.29

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Failed

Sandbox install failed

L5 · failed

ID: memory-eternal@0.10.29@dsh0.2.1-alpha.4 · profile: l4-sandbox

Issued: 2026-10-15 · expires: 2026-10-22

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-21

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-21

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-15

spec memory-eternal · channel npm package · outcome ran · exit 0

check took: 11.5s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-15

spec memory-eternal · channel npm package · outcome ran · exit 0

check took: 11.5s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-15

spec memory-eternal · channel npm package · outcome ran · exit 0

check took: 11.5s

L5 · Run tested✕ Failed

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-15

spec memory-eternal · install mode reused L4 scratch

check took: 0ms

Web boot readyL5.2_WEB_BOOT_READY✕ Failed

plugin tree failed to load

HTTP endpoint servedL5.3_HTTP_SERVED✕ Failed

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:

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.

memory-eternalAutomated review · daily

Static low, dynamic no conclusion — stricter wins → overall low.

static low→dynamic no conclusion→overall low

0 critical·0 high

lowoverall · low

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

Version binding

plugin versionv0.10.54dsh manifest

scanned version0.10.54npm2026-10-21

current version0.10.54same version

vet verdictclean · npm

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

show static findings (3)

warningfsWrite · fileslib/capture-log.js:29
await fs.appendFile(file, JSON.stringify(entry) + '\n', 'utf8')
warningfsWrite · fileslib/capture-log.js:62
await fs.writeFile(p, lines.slice(-CAPTURE_LOG_MAX_LINES).join('\n') + '\n', 'utf8')
warningfsWrite · fileslib/model-strikes.js:41
fs.writeFileSync(strikesPath(env), JSON.stringify({ version: 1, strikes: all }, null, 2), 'utf8')

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

not in the dynamic queue (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.

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-20 · activity: Active

• Repo created: 2026-08-31

• Stars: ★ 23 · Forks: 2

• Health: Active — committed within last 30 days

Source

GitHub: github.com/EternalNight996/memory-eternal

Plugin notes

What is the memory-eternal DeepSeek Harness plugin?

memory-eternal is a DeepSeek Harness plugin maintained by @EternalNight996. It is cataloged on dsh.so as a Knowledge 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 memory-eternal?

Run dsh plugin --profile web add memory-eternal in a DeepSeek Harness (dsh) environment. This exact command has been verified by a real install inside an isolated windows-acl sandbox (L4).

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, and its conclusion can only raise the combined verdict, never exempt it. 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-10-21

memory-eternal

What it doesAI

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README