registry / memgineering / 0.13.0
memgineering@0.13.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 shows the postinstall hook only prints global-install setup guidance. The apparent credential-forwarding behavior is scoped by an exact server URL match, so the scanner's malicious classification is not supported by an active attack in the inspected source.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user invokes the CLI operation that makes an authenticated API request.
Impact
No unauthorized credential exposure or other concrete attack impact was established.
Mechanism
The client compares the stored credential's service URL with the request base URL before using the token, then sends it as a bearer token.
AI rationale
Source inspection shows the postinstall hook only prints global-install setup guidance. The apparent credential-forwarding behavior is scoped by an exact server URL match, so the scanner's malicious classification is not supported by an active attack in the inspected source.
Evidence
package.jsonscripts/postinstall.mjsdist/index.js
Network endpoints1
api.memgineering.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs a script that prints setup guidance only for global installs; it does not perform setup itself.
- The bundled client permits an operator-configured API URL, but stored credentials are used only when their recorded server URL matches the request base URL.
- The client attaches the selected token as a bearer authorization header for API requests.
- The required integration location describes agent guidance installed into CLAUDE.md; it does not establish an attack.
Evidence against
- Credential lookup enforces exact server URL matching before returning a stored token.
- Sign-in is explicitly requested by the user before a token is collected, and the request is directed to that selected service.
- The endpoint defaults to the package's own API host; no unauthorized credential forwarding or other concrete attack was identified.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/index.jsView file
15function brandHome() {
L16: return process.env[BRAND.homeEnvVar] ?? join(homedir(), BRAND.homeDirName);
L17: }
...
L118: function isInteractive() {
L119: return Boolean(process.stdout.isTTY) && !jsonMode;
L120: }
L121: function printHuman(text) {
L122: if (!jsonMode) process.stdout.write(text + "\n");
L123: }
...
L134: for (let i = 0; i < input.length; i++) {
L135: const code = input.charCodeAt(i);
L136: if (code === 27 && input[i + 1] === "]" || code === 157) {
Critical
Credential Exfiltration
Findings
3 Critical3 High4 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
CriticalPrevious Version Dangerous Deltadist/index.js
HighInstall Time Lifecycle Scriptspackage.json
HighCredential Redirect Persistencedist/index.js
HighTrigger Reachable Credential Exfiltrationdist/index.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
Low
Affected versions and remediation
This report applies to memgineering@0.13.0.
See all versions of memgineering for other recorded verdicts.
- Review the evidence and your use of memgineering@0.13.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.