EternalNight996/memory-eternal
C3DeepSeek Harness 插件：对话自动沉淀为知识卡，配可检索知识库 + 知识图谱 + 审核中心；SQLite/纯 Markdown 存储，零第三方依赖。
★ 10+ · EternalNight996/memory-eternal source on GitHub · this plugin in the registry
EternalNight996/memory-eternal is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, network server in build output only, reads credential-class env vars.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×5 in authored code, e.g. index.js:1030, bin/dsh-memory.mjs:100 |
| network server in build output only | net_server_bundled | ×1 in build output only, e.g. lib/web.js:53 |
| reads credential-class env vars | token_env | GITEE_TOKEN |
Hooks it attaches
agent/inbox/claimed agent/turn-stopping loader/volatile-update
Outbound domains
gitee.com www.npmjs.com reactjs.org
Environment variables it reads
MEMORY_ETERNAL_SKIP_AUTO MEMORY_ETERNAL_NODE MEMORY_GRAPH_PROFILE GITEE_TOKEN MEMORY_VAULT_DIR
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.