hippo-memory@1.44.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-aiSource inspection shows that the flagged agent configuration changes are reached through the user-invoked init flow, while npm postinstall performs repair for an existing Codex wrapper and prints read-only prompts. The available excerpts do not establish a concrete attack or credential exposure.
Decision evidence
public snapshot- npm postinstall runs a wrapper repair and prints setup prompts; it does not perform first-time agent setup.
- The user-invoked init flow detects existing agent markers and appends hook configuration to an existing target file.
- The detected targets include Claude Code, Codex, Cursor, OpenClaw, OpenCode, and Pi configuration markers.
- The flagged capture excerpt reads Claude project directory entries; it does not establish credential collection or exfiltration.
- Provider code defines conventional vendor embedding endpoints; the inspected source did not establish an unrelated credential recipient.
- Prediction files map database row fields into records; their inspected excerpts show no attack behavior.
- The package has a postinstall hook, but its source repairs a previously opted-in Codex wrapper and prints read-only prompts.
- The inspection did not establish unconsented install-time agent configuration changes or a concrete attack chain.
Source & flagged code
9 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 · L98Findings
Affected versions and remediation
This report applies to hippo-memory@1.44.0.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.44.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.