hippo-memory@1.52.7
Memory for AI agents that learns what is wrong and stops repeating it. MCP server and hooks for Claude Code, Codex and Cursor. SQLite, zero runtime deps.
AI Security Review
scanned 14d ago · by lpm-firewall-aiClassify as suspicious because the explicit `hippo init` command can modify agent configuration, and static analysis coverage is incomplete. The inspected npm postinstall behavior does not establish unconsented first-time agent setup or another concrete attack.
Decision evidence
public snapshot- The CLI’s `init` path invokes hook setup unless `--no-hooks` is set.
- Hook setup detects agent files in the current project and patches existing instruction files, adding Hippo hook instructions.
- The npm `postinstall` script loads the package postinstall module.
- The postinstall module repairs a previously installed Codex wrapper and prints setup guidance; it does not perform first-time wrapper installation.
- The package’s agent integration behavior is a user-invoked configuration capability, so the reviewed source does not establish an active attack.
- The explicit `hippo init` command can modify existing agent instruction files in the current project, making this a real agent-configuration capability.
- Static analysis reported parse errors in several files, so a clean classification is not supported by complete analysis coverage.
Source & flagged code
6 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.7.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.52.7 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.