registry / @mnemonik/cli / 7.165.0
@mnemonik/cli@7.165.0
Mnemonik installer and local project helper
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no install hooks, and importing the package entry only re-exports modules. The flagged eval is used to construct WebAssembly callbacks, while the reviewed runtime sender transmits project context to a caller-provided server without collecting machine credentials.
Static reason
One or more suspicious static signals were detected.
Trigger
The command-line bootstrap runs when a user invokes the CLI; the package entry point only re-exports modules.
Impact
No unauthorized execution, credential collection, or unrelated data transmission was identified in the inspected paths.
Mechanism
The scanner evaluates callback strings embedded in a WebAssembly module. The inspected runtime helper posts caller-provided project context and a caller-provided bearer token to a caller-provided server.
AI rationale
The manifest has no install hooks, and importing the package entry only re-exports modules. The flagged eval is used to construct WebAssembly callbacks, while the reviewed runtime sender transmits project context to a caller-provided server without collecting machine credentials.
Network endpoints2
api.mnemonik.dev (default API origin)Caller-supplied server URL in dist/runtime/signers.js
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 declares no lifecycle scripts, and the package entry point only re-exports modules.
- The scanner eval builds a callback from strings embedded in its WebAssembly module; the Node loader reads the module from a file path.
- The hook POST helper receives its server and bearer token as arguments, and its payload contains project identity and repository fingerprint context.
Evidence against
- The scanner bundle contains eval and network-loading code, which merits review, but the inspected Node path loads a local file and the eval uses WebAssembly-provided callbacks.
- The runtime helper sends a bearer token, but the inspected code does not read credentials from the environment or include them in the project-context payload.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStrings
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 · L9235256var func = `(${args}) => { ${body} };`;
L5257: ASM_CONSTS[start] = eval(func);
L5258: }
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/scanner/service.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.165.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.165.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.