hippo-memory@1.52.2
Biologically-inspired memory for AI agents. Zero runtime deps, SQLite, MCP server, and an opt-in hosted TypeSafe Jev reranker. Decay, retrieval strengthening, consolidation.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe install lifecycle is limited to repair of an existing opted-in Codex wrapper and visible setup prompts. Explicit `hippo init` can mutate agent configuration, which warrants a warning under the user-command setup policy, but the inspected source does not establish malicious behavior.
Decision evidence
public snapshot- The install hook runs a postinstall script, whose package entry delegates to dist/postinstall.js.
- The postinstall path repairs a Codex wrapper only for users who previously opted in; otherwise it prints setup instructions.
- Running `hippo init` can detect existing agent configuration and install Hippo hooks or a plugin into it.
- The OpenCode plugin installer writes the package’s plugin source under the resolved plugin path.
- The inspected install path does not perform first-time agent integration; its Claude and Codex messages direct users to explicit setup commands.
- The flagged capture code reads Claude project transcript paths; the cited section does not show credential collection or network transmission.
Source & flagged code
7 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.
dist/embeddings.jsView on unpkg · L99Findings
Affected versions and remediation
This report applies to hippo-memory@1.52.2.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.52.2 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.