registry / @mnemonik/cli / 7.164.4
@mnemonik/cli@7.164.4
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 point only exposes modules. The flagged dynamic evaluation belongs to WebAssembly scanner support; the authenticated network request is part of the explicitly invoked installer’s readiness flow to the package service.
Static reason
One or more suspicious static signals were detected.
Trigger
Explicit CLI invocation or a caller using the exported library functions.
Impact
No unauthorized data collection, execution, or account action was found.
Mechanism
The scanner compiles WebAssembly for language parsing; the install flow reports readiness to the package’s service.
AI rationale
The manifest has no install hooks, and importing the package entry point only exposes modules. The flagged dynamic evaluation belongs to WebAssembly scanner support; the authenticated network request is part of the explicitly invoked installer’s readiness flow to the package service.
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts or runtime dependencies.
- The import entry point only re-exports modules; the CLI runs its bootstrap when invoked.
- The scanner’s eval sites build functions from WebAssembly module data, and its response-loading path compiles WebAssembly rather than evaluating JavaScript responses.
- The install flow sends readiness data to the package service at api.mnemonik.dev using the CLI bearer token.
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.164.4.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.164.4 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.