@echomem/mcp@1.4.64
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 hook, and the flagged configuration writes occur through explicit product setup commands. Credential forwarding targets the configured EchoMem API, while onboarding guards local-history access with consent; the scanner's redirect claim was not supported by inspected source.
Decision evidence
public snapshot- The manifest points to the CLI entrypoint and lists development, test, and prepack scripts; it has no npm install lifecycle hook.
- The scorer utilities locate session JSONL files under the user's Codex sessions directory and process local session data.
- The monitor reads the local Codex session index, while migration discovers user-created Claude session files.
- Agent hook writes run through explicit setup commands and add EchoMem hooks to the selected agent's configuration.
- Login sends the supplied token to the configured EchoMem API, which defaults to the package's EchoMem service; onboarding gates local-history access on consent.
- Runtime updates install this package version into its managed directory with npm scripts disabled; analytics filters sensitive fields before sending setup events.
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.64.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.64 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.