@echomem/mcp@1.4.53
EchoMem MCP bridge for cross-agent memory, local history import, and recall
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis package contains broad but product-aligned MCP memory and local-session features. It has no npm install lifecycle hook, and its self-staging update path explicitly disables lifecycle scripts.
Decision evidence
public snapshot- The manifest exposes a CLI but no install lifecycle hook.
- The running bridge can stage a newer release of itself through npm after an update check.
- Explicit setup can add command hooks to Codex configuration.
- The source-session feature reads local Codex session metadata.
- The local HUD can serve tracked raw session files.
- The self-install command uses npm's ignore-scripts option, so it does not trigger nested package lifecycle scripts.
- Hook installation is tied to setup options and names the installed hooks; it is not an npm install-time action.
- The HUD validates requested paths against its tracked-session list.
- No credential harvesting, secret exfiltration, opaque payload, or destructive behavior was found.
Source & flagged code
9 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.53.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.53 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.