hippo-memory@1.72.0
Make your agent's memory work like a brain. Hippo is long-term memory for coding agents.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe suspicious static signals resolve to package-aligned setup behavior: postinstall does not install agent hooks, while CLI initialization performs integrations and scheduling. The added sleep-offload code is consistent with server sleep processing, with no concrete attack behavior found in the inspected source.
Decision evidence
public snapshot- The manifest postinstall invokes a small wrapper that imports the optional dist postinstall entry.
- The postinstall entry only attempts repair of an already-installed Codex wrapper and prints setup nudges; it does not itself install hooks into agent settings.
- Agent hook detection is based on existing agent marker files, and integration writes are reached through the CLI init flow.
- Daily scheduling is part of init/setup and can be skipped through an environment setting or CLI flag.
- The added sleep offload file runs sleep work in a child process with a deadline; it shows no unrelated payload or exfiltration behavior.
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 dynamic require/import behavior.
dist/embeddings/transformers.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to hippo-memory@1.72.0.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.72.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.