hippo-memory@2.0.0
Make your agent's memory work like a brain. Hippo is long-term memory for coding agents.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe lifecycle hook delegates to a postinstall module that prints guidance and uses guarded repair behavior. Agent configuration changes and scheduling are associated with the explicit init flow, and the flagged child process supports package memory consolidation; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json runs a postinstall script that delegates to dist/postinstall.js.
- dist/cli/init.js detects existing agent markers, and integration changes are performed through the init flow; its patcher does not create missing instruction files.
- dist/cli/install-steps.js sets up a daily schedule only when invoked and honors the schedule opt-out.
- dist/server/sleep-offload.js spawns a package-owned child process to run memory consolidation with a timeout.
- dist/postinstall.js describes its Claude configuration check as read-only and directs users to run hippo init for setup.
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@2.0.0.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@2.0.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.