registry / @mnemonik/cli / 7.146.6
@mnemonik/cli@7.146.6
Mnemonik installer and local project helper
AI Security Review
scanned 11d ago · by lpm-firewall-aiStatic signals for evaluation and network access are explained by bundled runtime and product functionality; the inspected source did not establish an attack. The manifest has no lifecycle scripts, and the update path checks signed release metadata and package integrity.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI bootstrap runs when a user invokes the executable; no malicious automatic install trigger was found.
Impact
No malicious effect was established from the inspected behavior.
Mechanism
The reviewed update path verifies a signed release manifest and package integrity. The evaluation matches are in WebAssembly support code.
AI rationale
Static signals for evaluation and network access are explained by bundled runtime and product functionality; the inspected source did not establish an attack. The manifest has no lifecycle scripts, and the update path checks signed release metadata and package integrity.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest declares the CLI entrypoint and contains no npm lifecycle scripts; CLI execution routes through its bootstrap.
- The update path validates a signed release manifest and rejects a mismatch between its package version or integrity and npm metadata before installation.
- The dynamic evaluation match is in WebAssembly support glue that builds callbacks from module exports; the inspected source did not establish remote-response code execution.
- The reviewed launcher, installer, authentication, scanner, and project modules did not establish a concrete attack surface.
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.6.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.146.6 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.