registry / @mnemonik/cli / 7.167.1
@mnemonik/cli@7.167.1
Mnemonik installer and local project helper
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package has no install hooks, and the flagged evaluation is tied to WebAssembly scanner exports rather than remote response code. The observed network requests report installer readiness to Mnemonik’s own API, consistent with the package’s stated purpose.
Static reason
One or more suspicious static signals were detected.
Trigger
CLI bootstrap runs when the user invokes the executable; no package lifecycle scripts are defined.
Impact
No malicious impact identified.
Mechanism
The inspected eval handles callbacks generated from WebAssembly exports. Install readiness is sent to the package’s Mnemonik API as part of setup.
AI rationale
The package has no install hooks, and the flagged evaluation is tied to WebAssembly scanner exports rather than remote response code. The observed network requests report installer readiness to Mnemonik’s own API, consistent with the package’s stated purpose.
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, and has no lifecycle scripts or runtime dependencies.
- The CLI calls its bootstrap only when the executable is invoked without --help.
- The scanner’s eval constructs callbacks from WebAssembly module exports; the inspected code does not pass an HTTP response into eval.
- Install-session requests go to Mnemonik’s API, configurable through MNEMONIK_API_RESOURCE.
- The install flow reports readiness fields about selected projects to that API as part of the installer’s setup workflow.
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.167.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.167.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.