registry / @mnemonik/cli / 7.146.4
@mnemonik/cli@7.146.4
Mnemonik installer and local project helper
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the inspected self-update path verifies release signatures and integrity before installation. Static eval and process-execution signals resolve to bundled parser/runtime or product setup code; inspected source does not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the mnemonik CLI or invokes an exported package API.
Impact
No confirmed malicious impact or attack surface was established.
Mechanism
The updater checks registry metadata and verifies a signed release before installation; the eval findings occur in bundled WebAssembly parser tooling.
AI rationale
The package has no install lifecycle hook, and the inspected self-update path verifies release signatures and integrity before installation. Static eval and process-execution signals resolve to bundled parser/runtime or product setup code; inspected source does not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no lifecycle scripts; the executable starts the CLI bootstrap only when invoked.
- The self-update path compares registry metadata, verifies a signed release manifest and checks package integrity before installing an update.
- The flagged eval calls are in bundled WebAssembly parser tooling; source shows its language-loading and WebAssembly instantiation code.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
8 flaggeddist/diagnostics.jsView file
923import { createHash, createPublicKey, randomUUID, timingSafeEqual, verify as verifySignature } from "node:crypto";
L924: import { execFile, execFileSync } from "node:child_process";
L925: function windowsCommand(file) {
High
Child Process
Package source references child process execution.
dist/diagnostics.jsView on unpkg · L9235245var func = `(${args}) => { ${body} };`;
L5246: ASM_CONSTS[start] = eval(func);
L5247: }
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
1 Critical6 High4 Medium4 Low
CriticalRemote Response Code Executiondist/runtime/selfUpdate.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
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @mnemonik/cli@7.146.4.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.146.4 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.