Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.donggyun112/keymem

NPM · KEYMEM · SCANNED AUG 3

Associative key-graph memory for LLM agents — recall by association, not vector similarity.

Available components

+9 this week 33 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security79
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects tar 6.2.1, reached via fastembed > tar. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (176 of 177), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · keymem

# add to Claude Code
claude mcp add donggyun112-keymem -- npx -y keymem
# add to Codex CLI
codex mcp add donggyun112-keymem -- npx -y keymem
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "donggyun112-keymem": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "keymem"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add donggyun112-keymem --command npx --arg -y --arg keymem
# ~/.hermes/config.yaml
mcp_servers:
  donggyun112-keymem:
    command: "npx"
    args: ["-y", "keymem"]
// mcp.json
{
  "mcpServers": {
    "donggyun112-keymem": {
      "command": "npx",
      "args": [
        "-y",
        "keymem"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +28
    • CVE-2026-23745 affects this package: high security
    • CVE-2026-31802 affects this package: high security
    • CVE-2026-59871 affects this package: high security
    • GHSA-r292-9mhp-454m affects this package: high security
    • CVE-2026-53655 affects this package: high security
    • CVE-2026-59873 affects this package: high security
    • CVE-2026-24842 affects this package: high security
    • CVE-2026-29786 affects this package: high security
    • CVE-2026-23950 affects this package: high security
    • CVE-2026-59874 affects this package: high security
    • CVE-2026-59875 affects this package: high security
    • CVE-2026-26960 affects this package: high security
    • Known CVEs: unverified → fail security
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • Licence: MIT functional
  • 31 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 28 Jul 26 0
    • Security disclosure: unverified → fail functional
  • 27 Jul 26 24

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 12 findings
ID CVE Severity Vector Fix available
GHSA-23hp-3jrh-7fpw CVE-2026-59873 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-34x7-hfp2-rc4v CVE-2026-24842 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N yes
GHSA-83g3-92jg-28cx CVE-2026-26960 high CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N yes
GHSA-8qq5-rm4j-mr97 CVE-2026-23745 high yes
GHSA-8x88-c5mf-7j5w CVE-2026-59874 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9ppj-qmqm-q256 CVE-2026-31802 high yes
GHSA-gvwx-54wh-qm9j CVE-2026-59875 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-qffp-2rhf-9h96 CVE-2026-29786 high yes
GHSA-r292-9mhp-454m medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-r6q2-hw4h-h46w CVE-2026-23950 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L yes
GHSA-vmf3-w455-68vh CVE-2026-53655 medium yes
GHSA-w8wr-v893-vjvp CVE-2026-59871 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
Dependencies 176 packages

176 packages in the resolved dependency tree · 167 deprecated · 58 stale · 2 without a linked repository.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.