registry / @mnemonik/cli / 7.146.3
@mnemonik/cli@7.146.3
Mnemonik installer and local project helper
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior. The scanner's eval and execution signals correspond to embedded WebAssembly support and ordinary CLI setup, diagnostics, and update functions.
Static reason
One or more suspicious static signals were detected.
Trigger
No malicious trigger identified; the CLI runs when invoked, and package.json declares no lifecycle scripts.
Impact
No confirmed malicious impact identified.
Mechanism
The flagged dynamic evaluation is part of the embedded WebAssembly loader. Updates are checked against a signed release manifest and package integrity.
AI rationale
Source inspection found no concrete attack behavior. The scanner's eval and execution signals correspond to embedded WebAssembly support and ordinary CLI setup, diagnostics, and update functions.
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and module entrypoint, with no lifecycle scripts or runtime dependencies.
- Inspected scanner, project, installation, and authentication modules show local validation, journaled setup, and explicit sign-in plumbing.
- The flagged eval builds a function for the embedded WebAssembly runtime; it is not fed a remote response.
- The self-update path verifies a signed release manifest and package integrity before installing an update.
- The hook helper takes its server and bearer token as inputs and sends host/session context plus a hashed project identity.
Evidence against
- Static signals include eval, network, and child-process use, but inspected source places them in the WebAssembly loader and CLI setup, diagnostics, and update functionality.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
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.3.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.146.3 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.