hippo-memory@1.64.0
Make your agent's memory work like a brain. Hippo is long-term memory for coding agents.
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe install hook performs a guarded repair of an existing Codex wrapper, a concrete agent integration lifecycle risk. The metadata gate indicates prior opt-in, so the evidence supports a warning rather than a block.
Decision evidence
public snapshot- package.json runs scripts/postinstall.cjs during installation.
- The postinstall path invokes a Codex wrapper repair unless skipped.
- Repair requires existing wrapper metadata, then can re-run wrapper installation for a package in node_modules.
- Wrapper installation can move the Codex executable to a backup path.
- The init agent configuration changes are tied to explicit initialization behavior.
- The wrapper repair is gated by metadata indicating a prior opt-in; first-time installation is directed to an explicit CLI command.
- The Claude and Codex postinstall messages are read-only nudges, and the init flow supports skipping automatic integrations.
Source & flagged code
8 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/local-embedding.jsView on unpkg · L30Findings
Affected versions and remediation
This report applies to hippo-memory@1.64.0.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.64.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.