hippo-memory@1.38.1
Biologically-inspired memory system for AI agents. Decay by default, strength through use.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe code establishes a guarded automatic repair chain that can modify a Codex launcher after installation. It does not meet the stated block threshold because fresh installation requires explicit setup and no complete malicious lifecycle chain was found.
Decision evidence
public snapshot- The install lifecycle loads and runs the shipped postinstall module.
- Postinstall calls repair logic for an existing Codex wrapper.
- The repair path can replace a Codex launcher when Hippo metadata exists.
- The package text addresses supply-chain scanners while discussing binary replacement.
- No runtime dependency on another hippo-memory release is declared.
- First-time wrapper installation is limited to an explicit Hippo command.
- The inspected embedding requests use configured provider endpoints and API keys, not an unrelated collection host.
Source & flagged code
11 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/rerankers/cross-encoder.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to hippo-memory@1.38.1.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.38.1 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.