dsh.so
EN
English中文
@ystyle/chronomem avatar

@ystyle/chronomem

忆时塔 chronomem：以 MCP 服务形态提供的时间分层外部记忆（回想 + 语义总结）——含 dsh 会话活动采集插件

Ecosystem pluginKnowledgeContentMemoryStorage
Verification
L5 · Ecosystem plugin
Ecosystem plugin
Risk
LowRisk
Health
Active
Trust
Silver

Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →

What it doesAI

MCP service that keeps time-layered external memory per custom memory type, with zero-LLM drill-down recall and LLM semantic summaries.

  • Hierarchical time buckets (10min to week) per custom memory type
  • Zero-LLM exact recall drills down to raw entries via reference chain
  • LLM semantic summaries per time range, recursively condensable
knowledgeAImemoryAIstorageAI

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:ystyle/chronomem
verified

Install method: GitHub · runtime test inconclusive (L5 unknown)

Verification & Compatibility○ Ecosystem plugin

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
package manifest not collected

package manifest not collected — the declared range is unknown.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
○ Ecosystem plugin
At-a-glance → evidence in the cards below
plugin ＼ dshdsh 0.2.1-rc.2
current
dsh 0.2.1-alpha.4dsh 0.2.1-alpha.2
e2f4c9○○○
27b9fc···
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
e2f4c9github○ 3 ecosystem plugin2026-10-19

https://github.com/ystyle/chronomem

○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.2
  • • Plugin artifact: github · https://github.com/ystyle/chronomem (version unstated)
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
Unknown
Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)
Ecosystem plugin

ID: chronomem@e2f4c9@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-19 · expires: 2026-10-26

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-18
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-18
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec github:ystyle/chronomem · channel GitHub source · outcome ran · exit 0
check took: 2.6s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec github:ystyle/chronomem · channel GitHub source · outcome ran · exit 0
check took: 2.6s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec github:ystyle/chronomem · channel GitHub source · outcome ran · exit 0
check took: 2.6s
L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec github:ystyle/chronomem · install mode reused L4 scratch
check took: 54ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-10-19
ready line dsh web: http://127.0.0.1:49817/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-10-19
path / · HTTP 200 · took 54ms
Plugin active in inventory? Unknown
Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-19
verdict not-found · entries 149
phases: active 121 · null 28
not present in web-profile loader inventory

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-18Ecosystem plugin
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.4
  • • Plugin artifact: github · https://github.com/ystyle/chronomem (version unstated)
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
Unknown
Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)
Ecosystem plugin

ID: chronomem@e2f4c9@dsh0.2.1-alpha.4 · profile: l3-fullscan

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

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-18
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-18
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec github:ystyle/chronomem · channel GitHub source · outcome ran · exit 0
check took: 2.0s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec github:ystyle/chronomem · channel GitHub source · outcome ran · exit 0
check took: 2.0s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec github:ystyle/chronomem · channel GitHub source · outcome ran · exit 0
check took: 2.0s
L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec github:ystyle/chronomem · install mode reused L4 scratch
check took: 1.3s
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-10-17
ready line dsh web: http://127.0.0.1:64190/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-10-17
path / · HTTP 200 · took 1.3s
Plugin active in inventory? Unknown
Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-17
verdict not-found · entries 149
phases: active 121 · null 28
not present in web-profile loader inventory

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-14Ecosystem plugin
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.2
  • • Plugin artifact: github · https://github.com/ystyle/chronomem (version unstated)
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
Unknown
Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)
Ecosystem plugin

ID: chronomem@e2f4c9@dsh0.2.1-alpha.2 · profile: l4-sandbox

Issued: 2026-10-14 · expires: 2026-10-21

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-18
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-18
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec github:ystyle/chronomem · channel GitHub source · outcome ran · exit 0
check took: 2.1s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec github:ystyle/chronomem · channel GitHub source · outcome ran · exit 0
check took: 2.1s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec github:ystyle/chronomem · channel GitHub source · outcome ran · exit 0
check took: 2.1s
L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec github:ystyle/chronomem · install mode reused L4 scratch
check took: 133ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-10-14
ready line dsh web: http://127.0.0.1:49675/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-10-14
path / · HTTP 200 · took 133ms
Plugin active in inventory? Unknown
Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-14
verdict not-found · entries 149
phases: active 121 · null 28
not present in web-profile loader inventory

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

27b9fclocal2026-10-14

Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.

Author badges

Embed the official badges in your README to showcase security & install-test status:

dsh.so risk
`[![dsh.so risk](https://www.dsh.so/badge/chronomem.svg)](https://www.dsh.so/artifact/chronomem/)`

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.

chronomemAutomated review · daily

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

static low→dynamic low→overall low
0 critical·0 high1 medium-risk findings hidden
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
Version binding
plugin version—
scanned version94fb70806ea8git2026-10-21
current version94fb70806ea8same version
vet verdictclean · git

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

show static findings (12)
  • warningcurlDownload · networkbench/airamcp.sh:24

    SID=$(curl -s -D - -o /dev/null -m 30 --noproxy '*' -X POST "$ENDPOINT" \

  • warningcurlDownload · networkbench/airamcp.sh:30

    curl -s -o /dev/null -m 20 --noproxy '*' -X POST "$ENDPOINT" \

  • warningnetIp · networkdocs/ui/scripts/audit-overflow.sh:6

    BASE=http://127.0.0.1:18901

  • warningnetIp · networkdocs/ui/scripts/diag-click.sh:7

    agent-browser open http://127.0.0.1:8901 2>&1 | tail -1

  • warningnetIp · networkdocs/ui/scripts/diag-dropdown.sh:5

    BASE=http://127.0.0.1:18901

  • warningnetIp · networkdocs/ui/scripts/diag-hit.sh:7

    agent-browser open http://127.0.0.1:8901 2>&1 | tail -1

  • warningnetIp · networkdocs/ui/scripts/diag-inst.sh:7

    agent-browser open http://127.0.0.1:8901 --init-script /home/ystyle/Projects/Cangjie/chronomem/docs/ui/scripts/count-inst.js >/dev/null 2>&1

  • warningnetIp · networkdocs/ui/scripts/diag-mouse.sh:7

    agent-browser open http://127.0.0.1:8901 2>&1 | tail -1

  • warningnetIp · networkdocs/ui/scripts/diag-mouse2.sh:7

    agent-browser open http://127.0.0.1:8901 2>&1 | tail -1

  • warningnetIp · networkdocs/ui/scripts/diag-msg.sh:7

    agent-browser open http://127.0.0.1:8901 >/dev/null 2>&1

  • warningnetIp · networkdocs/ui/scripts/diag-send.sh:7

    agent-browser open http://127.0.0.1:8901 >/dev/null 2>&1

  • warningnetIp · networkdocs/ui/scripts/stats.sh:9

    agent-browser open http://127.0.0.1:8900 >/dev/null 2>&1

2dynamic auditmodel reads redacted source context · never executes plugin code
highest gradelow
merged intooverall low
audited at2026-10-17
findings0 critical·0 high0 medium / 2 low hidden
show 2 audit findings
  • lowDeveloper host paths hard-coded in test scriptsdocs/ui/scripts/tour.sh:5

    Absolute home-directory paths (also in diag-inst.sh:7 '--init-script /home/ystyle/Projects/Cangjie/chronomem/docs/ui/scripts/count-inst.js' and diag-mouse.sh screenshot dir) disclose the maintainer's local username and project layout in a published artifact. No runtime reachability: these are manually run dev scripts, so there is no exploit path, only information disclosure.

  • lowBridge row is an untagged root listener observing every agent's eventsdsh-mem-bridge/cordis.patch.yml:9

    By design and by disclosure, the mem-bridge instance is mounted globally, so it receives the event stream of every agent in the profile rather than a scoped subset. This is the plugin's stated purpose (memory capture) and the config is empty, but it widens the data surface the bridge can persist. Impact cannot be fully assessed here because the bridge implementation was not part of the harvest.

Harvested files are developer test/bench tooling plus a bundle-patch YAML; no plugin runtime code, no reachable secret, shell or network abuse.

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

• Repo created: 2026-10-13

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/ystyle/chronomem

Was this page helpful?