hippo-memory@1.38.10
Biologically-inspired memory system for AI agents. Decay by default, strength through use.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source does not establish payload theft, remote execution, or an unconsented first-install wrapper takeover. It does establish a guarded automatic lifecycle mutation of a foreign AI-agent launcher and reviewer-directed scanner language.
Decision evidence
public snapshot- The postinstall hook automatically loads package code that can repair an existing Codex launcher wrapper.
- The repair path can rename the detected Codex executable and replace it with a Hippo wrapper when prior Hippo metadata is present.
- Package comments explicitly discuss how the behavior appears to security scanners, which is reviewer-directed text.
- Configured embedding providers send supplied text and the selected provider key to OpenAI, Voyage, or Cohere.
- A first install does not create the Codex wrapper unless Hippo metadata already exists.
- The initial Codex wrapper installation is only reached through the explicit `hippo hook install codex` command.
- No self-dependency or opaque payload download was present in package.json.
- The dynamic import only loads optional local transformer packages.
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 dynamic require/import behavior.
dist/rerankers/cross-encoder.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to hippo-memory@1.38.10.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.38.10 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.