registry / @mnemonik/cli / 7.169.0
@mnemonik/cli@7.169.0
Mnemonik installer and local project helper
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install hooks, and the CLI’s reviewed dynamic evaluation belongs to its WebAssembly scanner loader. Network reporting occurs during the user-run install workflow and targets Mnemonik’s own API.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI runs when a user invokes the mnemonik command; install reporting occurs in its installation workflow.
Impact
No malicious impact was identified in the reviewed source.
Mechanism
The scanner loads WebAssembly language modules, and the install workflow reports readiness to the configured Mnemonik API using an existing bearer token.
AI rationale
The manifest has no install hooks, and the CLI’s reviewed dynamic evaluation belongs to its WebAssembly scanner loader. Network reporting occurs during the user-run install workflow and targets Mnemonik’s own API.
Network endpoints2
api.mnemonik.devMNEMONIK_API_RESOURCE-configured API origin
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts or runtime dependencies.
- The CLI calls its bootstrap when a user runs the command.
- The scanner fetches a language module and compiles it as WebAssembly.
- The eval sites build callbacks from JavaScript glue stored in the WebAssembly module.
- Install readiness is reported to Mnemonik’s API using an existing bearer token.
- The API host defaults to api.mnemonik.dev and can be set through MNEMONIK_API_RESOURCE.
Evidence against
- Bundled files contain process execution and dynamic evaluation, but the reviewed contexts serve CLI setup, Git inspection, and WebAssembly loading.
- The package performs network requests during its install workflow, but the reviewed report sends readiness data to the package’s own API.
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.169.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.169.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.