registry / hippo-memory / 1.67.0
hippo-memory@1.67.0
Make your agent's memory work like a brain. Hippo is long-term memory for coding agents.
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection shows that postinstall is limited to repairing an already installed Codex wrapper and printing read-only guidance. Agent integration and scheduling writes are activated through user-invoked CLI setup, so the scanner hints do not establish an attack.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall prints guidance and conditionally repairs an existing wrapper; agent configuration and scheduling occur when the user runs Hippo setup commands.
Impact
No confirmed malicious effect or unauthorized control-surface mutation was established.
Mechanism
Postinstall does not install new agent integrations. The CLI setup flow adds integrations to detected agent configurations, while the scheduler stores workspace registration data.
AI rationale
Source inspection shows that postinstall is limited to repairing an already installed Codex wrapper and printing read-only guidance. Agent integration and scheduling writes are activated through user-invoked CLI setup, so the scanner hints do not establish an attack.
Evidence
package.jsonscripts/postinstall.cjsdist/postinstall.jsdist/cli/init.jsdist/cli/setup.jsdist/scheduler.jsdist/cli/shared.js
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The install hook loads a package-local postinstall module; that module repairs an already installed Codex wrapper and otherwise prints read-only setup guidance.
- The agent configuration locations are detected during init, which only adds integrations when the user runs init and has not disabled them.
- The hook install behavior is exposed through an explicit hippo hook install command.
- The scheduler writes its workspace registry as part of the package's user-invoked setup flow.
- Hook execution runs through bounded store handling; no attack behavior was identified in the reviewed paths.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/local-embedding.jsView file
31// Promise<object> names that honestly without claiming a specific module shape.
L32: const _dynImport = new Function('s', 'return import(s)');
L33: /** Check (synchronously) if @xenova/transformers or @huggingface/transformers is installed. */
Low
Eval
Package source references a known benign dynamic code generation pattern.
dist/local-embedding.jsView on unpkg · L31Findings
4 High6 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/cli/setup.js
HighTrigger Reachable Persistencedist/scheduler.js
HighSemantic Analysis Limiteddist/cli/shared.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/rerankers/cross-encoder.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/scheduler.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvaldist/local-embedding.js
Affected versions and remediation
This report applies to hippo-memory@1.67.0.
See all versions of hippo-memory for other recorded verdicts.
- Review the evidence and your use of hippo-memory@1.67.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.