memgineering@0.23.0
One memory for the AI you connect. Recall, remember, and revise a brain your agents share — stored in your own folder.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package contains a concrete install-time prompt-injection chain into persistent AI-agent configuration, but the hook itself only prints and no secret exfiltration or self-dependent lifecycle chain was verified. This warrants a warning rather than a block under the install-control-surface policy.
Decision evidence
public snapshot- The install hook addresses an AI agent directly and instructs it to run setup immediately rather than stop for the user.
- The prompted setup opens a browser and, after a remote session completes, can write guides, skills, and hooks into detected AI-agent homes.
- This is an install-time social-engineering path toward persistent agent control-surface changes.
- The postinstall script itself only prints when globally installed; it does not directly modify files or send data.
- No self-dependency, obfuscated payload, or environment-secret harvesting was found.
- The default API host is package-aligned, and credentials are stored locally after its device-login flow.
Source & flagged code
6 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 unpkgFindings
Affected versions and remediation
This report applies to memgineering@0.23.0.
See all versions of memgineering for other recorded verdicts.
- Review the evidence and your use of memgineering@0.23.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.