memgineering@0.26.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 13d ago · by lpm-firewall-aiSource inspection found that installation only prints global setup guidance and does not perform agent setup. The agent configuration path is separate from installation, and the inspected telemetry path is opt-in and sends error details rather than credentials.
Decision evidence
public snapshot- The manifest runs scripts/postinstall.mjs after installation.
- The postinstall script prints setup guidance only for global installs; setup is a separate command.
- The required Claude guidance location describes generated agent instructions, not executable code.
- Setup obtains its configuration through the CLI action, and an interactive run asks how to proceed.
- Error telemetry is gated on the saved errorTelemetry setting being on.
- Registry client construction uses the configured registry API URL or the Kordis default.
- The inspected install hook does not itself run agent setup or write agent configuration.
- The inspected telemetry payload contains error and runtime details, not credentials.
Source & flagged code
7 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.26.0.
See all versions of memgineering for other recorded verdicts.
- Review the evidence and your use of memgineering@0.26.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.