registry / @mnemonik/cli / 7.141.0
@mnemonik/cli@7.141.0
Mnemonik installer and local project helper
AI Security Review
scanned 19d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior. The scanner’s evaluation matches are bundled WebAssembly support, and the manifest defines no npm lifecycle hooks.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI runs when invoked; the package manifest has no npm lifecycle scripts.
Impact
No unconsented credential disclosure, harmful account action, or install-time mutation was identified.
Mechanism
The inspected credential paths read local credential files or the operating system keychain and select Mnemonik-associated entries. The updater checks signed release metadata and package integrity.
AI rationale
Source inspection found no concrete attack behavior. The scanner’s evaluation matches are bundled WebAssembly support, and the manifest defines no npm lifecycle hooks.
Decision evidence
public snapshotAI called this Clean at 85.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares no npm lifecycle scripts, and the CLI entrypoint invokes its bootstrap only when the command runs.
- The flagged eval matches construct wrappers for bundled WebAssembly modules; the updater separately checks signed release metadata and package integrity.
- The Claude and Codex helpers read local saved credentials and select entries associated with the Mnemonik server declaration; the inspected excerpts show no credential send.
- The signer source performs a cryptographic digest operation.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
9 flaggeddist/diagnostics.jsView file
919import { createHash, createPublicKey, randomUUID, timingSafeEqual, verify as verifySignature } from "node:crypto";
L920: import { execFile, execFileSync } from "node:child_process";
L921: function windowsCommand(file) {
High
Child Process
Package source references child process execution.
dist/diagnostics.jsView on unpkg · L9195244var func = `(${args}) => { ${body} };`;
L5245: ASM_CONSTS[start] = eval(func);
L5246: }
High
1import { createRequire as __createRequire } from "node:module"; const require = __createRequire(import.meta.url);
L2: var __create = Object.create;
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/diagnostics.jsView on unpkg · L1Findings
2 Critical6 High4 Medium4 Low
CriticalRemote Response Code Executiondist/runtime/selfUpdate.js
CriticalPrevious Version Dangerous Deltadist/runtime/signers.js
HighChild Processdist/diagnostics.js
HighEvaldist/diagnostics.js
HighSame File Env Network Executiondist/install/journey.js
HighCommand Output Exfiltrationdist/runtime/signers.js
HighSandbox Evasion Gated Capabilitydist/install/journey.js
HighCross File Remote Execution Contextdist/auth/credentials.js
MediumDynamic Requiredist/diagnostics.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @mnemonik/cli@7.141.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.141.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.