registry / @mnemonik/cli / 7.170.1
@mnemonik/cli@7.170.1
Mnemonik installer and local project helper
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest and inspected code match a CLI installer and local project helper. The scanner’s eval is used to instantiate WebAssembly-provided callbacks, while install reporting uses the package’s own API when a CLI bearer is available.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI bootstrap runs when invoked; scanner callbacks are created when the WebAssembly scanner initializes, and install-session reporting runs when a CLI bearer is available.
Impact
No malicious collection, unrelated remote execution, or unrequested account action was identified in the reviewed paths.
Mechanism
The scanner builds JavaScript callbacks from WebAssembly module exports. Install reporting uses bearer-authenticated requests to the configured Mnemonik API origin.
AI rationale
The manifest and inspected code match a CLI installer and local project helper. The scanner’s eval is used to instantiate WebAssembly-provided callbacks, while install reporting uses the package’s own API when a CLI bearer is available.
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes an installer and local project helper, exposes a CLI entry point, and has no lifecycle scripts or runtime dependencies.
- The scanner’s eval calls construct callbacks from strings exported by its WebAssembly module as part of the bundled Emscripten runtime.
- Install-session reporting is conditional on obtaining the CLI bearer and targets the Mnemonik API origin.
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 · 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.170.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.170.1 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.