registry / memgineering / 0.15.1
memgineering@0.15.1
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 a global-install notice, a separate setup flow, and URL-bound credential use. The scanner’s credential-forwarding hint is not supported as an attack by these inspected paths.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Package installation triggers the postinstall notice; setup and sign-in require a later command or interactive choice.
Impact
The inspected code does not establish unconsented agent configuration changes or forwarding a saved credential to a different API URL.
Mechanism
The notice writes to standard output. API requests use the configured memgineering API URL, and saved credentials are used only when their stored URL matches it.
AI rationale
Source inspection found a global-install notice, a separate setup flow, and URL-bound credential use. The scanner’s credential-forwarding hint is not supported as an attack by these inspected paths.
Evidence
package.jsonscripts/postinstall.mjsdist/index.js
Network endpoints1
api.memgineering.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs a postinstall script; that script prints setup guidance only when npm reports a global install.
- Stored credentials are used only when their saved API URL matches the current API URL; interactive setup asks whether to sign in.
- The required agent integration location describes how the package organizes its guidance, without establishing an attack.
Evidence against
- The postinstall hook does not perform setup or modify agent configuration; the setup command is separate.
- The API defaults to the package’s hosted service, and the inspected credential flow does not forward a saved token after the configured API URL changes.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
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.15.1.
See all versions of memgineering for other recorded verdicts.
- Review the evidence and your use of memgineering@0.15.1 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.