registry / memgineering / 0.9.1
memgineering@0.9.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 shows a global-only postinstall message and an issuer match before stored credentials are used. The flagged agent location is explanatory bundled text, and the inspected code does not establish an active attack surface.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Package installation; setup is described as a later user-guided action.
Impact
No confirmed credential exposure or unconsented agent configuration change was established.
Mechanism
The global postinstall branch writes setup guidance to stdout. The API client chooses the configured or default service URL, and the inspected caller refuses credentials when their saved issuer differs.
AI rationale
Source inspection shows a global-only postinstall message and an issuer match before stored credentials are used. The flagged agent location is explanatory bundled text, and the inspected code does not establish an active attack surface.
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 routes postinstall to a script that only prints setup guidance when npm installs globally.
- The postinstall guidance says setup is not run there because it asks the user what to install and whether the tool may update itself.
- The API URL defaults to the package service, and credentials are used only when their saved issuing URL matches the active URL.
- The flagged dist location is explanatory text about the setup hub; it does not perform an agent configuration write.
Evidence against
- The CLI supports an operator-configured API URL, but the inspected credential path checks that URL against the saved credential issuer before use.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
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.9.1.
See all versions of memgineering for other recorded verdicts.
- Review the evidence and your use of memgineering@0.9.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.