superlocalmemory@4.1.9
Local-first agent memory with MCP and an agent-native CLI. Documented clients include Claude Code, Cursor, and Windsurf.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe automatic lifecycle behavior is limited in the inspected source to installing this package into a private runtime inside its own package directory. The flagged hooks dispatch user-facing memory commands, and the inspected destructive reset path requires confirmation; no concrete malicious behavior was found.
Decision evidence
public snapshot- The npm postinstall runs the package installer; it creates a Python environment inside the package and pip-installs from that package directory.
- The interactive configurator runs only when invoked directly.
- The flagged memory hooks pass their requested list, profile, recall, or remember action to the package CLI; reset requires explicit confirmation for full deletion.
- The vendor JavaScript begins with a standard UMD module wrapper.
- No inspected source showed credential collection, exfiltration, remote code loading, or writes to a foreign agent configuration surface.
- The installer targets a package-owned runtime, while destructive reset actions require user confirmation.
Source & flagged code
13 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references a known benign dynamic code generation pattern.
src/superlocalmemory/ui/vendor/d3.v7.min.jsFindings
Affected versions and remediation
This report applies to superlocalmemory@4.1.9.
See all versions of superlocalmemory for other recorded verdicts.
- Review the evidence and your use of superlocalmemory@4.1.9 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.