@echomem/mcp@1.4.66
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 flagged code inspected performs local history integration, setup-time hook configuration, and requests to the configured EchoMem API. These source facts do not establish malicious behavior.
Decision evidence
public snapshot- package.json has no preinstall, install, or postinstall hook; its listed scripts are build, development, test, and prepack commands.
- The scorer assets locate Codex session files, and the HUD monitor reads the session index; these are local history utilities.
- The migration helper recognizes Claude Cowork session paths, consistent with local history import.
- Setup resolves agent configuration directories from the user's profile paths and writes EchoMem hooks through a setup helper.
- Authenticated setup requests use the configured EchoMem API base URL; the HUD sends its saved token to that same configured service.
- The background runtime updater is called with the latest version reported by the package's update check.
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.66.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.66 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.