mcp-agents-memory@0.9.30
Long-term memory for AI agents with provenance tracking
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged Typesafe request is an optional project-tagging feature gated by JEV_ENABLED=true and uses a Typesafe key with the Typesafe endpoint. The OpenAI client uses the standard OpenAI key and service, while the manifest's prepare script runs only true.
Decision evidence
public snapshot- The manifest exposes build/index.js as the package entry and CLI; its prepare script runs only true.
- The Typesafe judge is gated on JEV_ENABLED being exactly true.
- The judge sends requests to api.typesafe.ai using a Typesafe API key, not an OpenAI key.
- The OpenAI client uses OPENAI_API_KEY with its default OpenAI service endpoint.
- The optional Typesafe judge reads project memory messages and candidate tags for its request.
- The judge can read a key from the fixed path /home/admin_3alab/.config/typesafe/api_key when enabled.
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.30.
See all versions of mcp-agents-memory for other recorded verdicts.
- Review the evidence and your use of mcp-agents-memory@0.9.30 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.