@echomem/mcp@1.4.57
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 npm install lifecycle hook, and inspected runtime behaviors are tied to EchoMem functionality or explicit setup. The scanner’s flagged locations did not establish a concrete attack surface.
Decision evidence
public snapshot- package.json defines the CLI entry point and ordinary development scripts, with no install lifecycle hook.
- The flagged asset and migration code reads local agent session indexes and transcript paths as part of its product functionality.
- HUD hooks are installed through explicit functions and add EchoMem callbacks to user settings.
- Runtime updates install the requested EchoMem version into managed staging with npm scripts disabled.
- The default API endpoint is EchoMem’s service; the bearer token is sent through a client configured for that 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.57.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.57 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.