mcp-agents-memory@0.9.18
Long-term memory for AI agents with provenance tracking
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source shows package-aligned memory processing and database migrations, with no install-time attack chain or foreign agent configuration writes. The flagged location reads transcripts, and optional service authentication uses the credential's intended destination.
Decision evidence
public snapshot- package.json has no install hooks or runtime dependencies; prepare is a no-op.
- The flagged Claude projects location supports transcript capture, without agent configuration mutation.
- Transcript capture starts with the memory server and stores parsed messages in the configured database.
- The required migration adds librarian bookkeeping columns using database transactions.
- Optional Typesafe classification requires explicit enablement and authenticates requests to its fixed service endpoint.
Source & flagged code
31 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.18.
See all versions of mcp-agents-memory for other recorded verdicts.
- Review the evidence and your use of mcp-agents-memory@0.9.18 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.