hippo-memory@1.51.0
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 package has an install hook, but source shows that agent setup is tied to explicit `hippo init`; postinstall repair applies only to an existing Codex wrapper. The guarded agent integration is a warning-level capability, with no source evidence of an unconsented install-time control-surface mutation or other attack.
Decision evidence
public snapshot- `hippo init` calls hook auto-install unless `--no-hooks` is set.
- The CLI detects agent configuration across Claude Code, Codex, Cursor, OpenClaw, OpenCode, and Pi projects.
- The npm postinstall only repairs a Codex wrapper already installed by a user and prints setup nudges.
- Embedding requests send redacted text and an authorization key to the configured provider URL.
- Capture reads Claude project session files; predictions imports database and memory modules.
- The agent configuration changes are reached from the explicit `hippo init` command, not the npm install hook.
- The postinstall repair is limited to an existing Codex wrapper; first-time setup is an explicit CLI action.
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.51.0.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.51.0 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.