mcp-agents-memory
Long-term memory for AI agents with provenance tracking
This report shows the evidence for mcp-agents-memory@0.9.32. 0 of 11 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest's prepare hook is inert. The only concerning external flow found is an explicitly enabled tagging feature that sends the memory text it processes to the Typesafe endpoint using a Typesafe API key; this matches the package feature and does not establish malicious behavior.
Decision evidence
public snapshot- The package's prepare script is `true`; the manifest shows no install-time action.
- The Jev judge runs only when `JEV_ENABLED` is exactly `true`, and its key comes from `TYPESAFE_API_KEY` or a Typesafe key file.
- The judge sends the memory message and tagging context to the Typesafe endpoint for project-tag selection.
Source & flagged code
35 flaggedPackage contains a critical-looking secret pattern.
build/migrations/023_librarian_gate.jsView on unpkg · L9195RSA private key in build/migrations/023_librarian_gate.js
build/migrations/023_librarian_gate.jsView on unpkg · L9195Package source references child process execution.
build/migrations/023_librarian_gate.jsView on unpkg · L12898Findings
Affected versions and remediation
This report applies to mcp-agents-memory@0.9.32.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of mcp-agents-memory@0.9.32 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.