hippo-memory@1.43.2
Biologically-inspired memory system for AI agents. Decay by default, strength through use.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe package has an install-time path that can restore a previously opted-in Codex wrapper. Its metadata guard and explicit setup flow do not establish unconsented control-surface mutation, but the lifecycle repair remains a concrete integration risk.
Decision evidence
public snapshot- package.json runs a postinstall script.
- Postinstall repairs a Codex wrapper only when existing metadata records prior opt-in.
- The repair path can restore the wrapper during package installation.
- Explicit hook setup writes commands into agent settings.
- Postinstall does not perform a first-time Codex wrapper install.
- Claude Code hooks are installed through an explicit CLI command.
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.43.2.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.43.2 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.