@echomem/mcp@1.4.67
EchoMem MCP bridge for cross-agent memory, local history import, and recall
AI Security Review
scanned 19d ago · by lpm-firewall-aiStatic hints were verified against source: the package has no npm lifecycle hook, and the agent configuration changes occur through setup behavior. Inspected network and session-discovery code is consistent with the stated EchoMem integration, with no concrete attack behavior found.
Decision evidence
public snapshot- package.json declares no preinstall, install, or postinstall hook; its runtime entry is dist/index.js.
- The scorer assets locate and count turns in local Codex session files; the inspected paths show local session discovery.
- The HUD monitor reads Codex session index metadata to detect changes.
- Migration code identifies Claude session files under the local Claude projects directory.
- Setup resolves the Claude configuration directory and runs agent guidance, skill, and hook setup as part of the explicit setup flow.
- The durable runtime installs this package version for an ephemeral npx invocation; this is runtime setup, not a package lifecycle hook.
- The setup client uses the EchoMem API base URL for authenticated requests, consistent with the package's stated service.
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.67.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.67 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.