@echomem/mcp@1.4.59
EchoMem MCP bridge for cross-agent memory, local history import, and recall
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected findings map to local session discovery, HUD behavior, and explicit setup/runtime functions. The scanner’s severe labels were not substantiated as attack behavior by the inspected source excerpts.
Decision evidence
public snapshot- package.json defines a CLI entrypoint and has no preinstall, install, or postinstall hook.
- A scorer helper searches local Codex session files by session identifier.
- Another scorer helper matches values against a local Codex session index.
- The HUD monitor reads the local Codex session index to display titles.
- Migration code identifies local Claude session paths for import discovery.
- Setup resolves Codex and Claude configuration directories from environment settings or standard local directories.
- The durable entrypoint uses child-process support alongside runtime path resolution.
- The HUD server defaults to the EchoMem service and account site, with an environment override for the API base.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/durable-entry.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @echomem/mcp@1.4.59.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.59 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.