hippo-memory@1.42.0
Biologically-inspired memory system for AI agents. Decay by default, strength through use.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe flagged postinstall and agent-configuration behavior is bounded: postinstall does not perform first-time agent setup, and hook installation is user-invoked. The inspected prediction, capture, and embedding-provider code does not establish malicious behavior or unrelated credential forwarding.
Decision evidence
public snapshot- package.json defines a postinstall script that loads the package’s postinstall module.
- The postinstall module repairs a Codex wrapper only if one is already installed and prints setup instructions; it does not perform first-time wrapper installation.
- The `hippo init` path calls hook installation, and its detectors look for agent configuration in the current project.
- The capture and prediction files contain ordinary package functionality; the two prediction files have identical inspected source at the cited location.
- The embedding provider batches text for its configured provider; the inspected code does not establish credential forwarding to an unrelated recipient.
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/embeddings.jsView on unpkg · L98Findings
Affected versions and remediation
This report applies to hippo-memory@1.42.0.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.42.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.