hippo-memory@1.39.0
Biologically-inspired memory system for AI agents. Decay by default, strength through use.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package contains a real install-time launcher-repair capability, but the source limits it to an already configured integration and exposes first installation through an explicit command. This warrants a warning for lifecycle extension risk rather than a malware block.
Decision evidence
public snapshot- The automatic postinstall imports code that repairs an existing Codex launcher wrapper.
- The repair path runs whenever its metadata file exists and can reinstall the wrapper.
- The explicit hook command renames the detected Codex launcher and writes a replacement wrapper.
- The postinstall does not perform a first wrapper installation when metadata is absent.
- Launcher replacement is exposed through an explicit `hippo hook install codex` command.
- Network embedding requests use user-configured providers and their corresponding environment key.
Source & flagged code
9 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.39.0.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.39.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.