registry / @mnemonik/cli / 7.166.0
@mnemonik/cli@7.166.0
Mnemonik installer and local project helper
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts or runtime dependencies, and the import entry only re-exports modules. The flagged evaluation is part of WebAssembly support, while the reviewed hook network flow sends project context to the configured Mnemonik API.
Static reason
One or more suspicious static signals were detected.
Trigger
Explicit CLI or hook operations; no install lifecycle hook is configured.
Impact
No unauthorized credential transfer, concealed remote execution, or unrelated automatic action was identified.
Mechanism
Scanner code loads WebAssembly, and hook code can send project identity and a repository fingerprint to the configured Mnemonik API.
AI rationale
The manifest has no lifecycle scripts or runtime dependencies, and the import entry only re-exports modules. The flagged evaluation is part of WebAssembly support, while the reviewed hook network flow sends project context to the configured Mnemonik API.
Network endpoints1
api.mnemonik.dev
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 defines no lifecycle scripts or runtime dependencies.
- The package is an installer and local project helper; its import entry re-exports modules.
- The scanner fetches and compiles WebAssembly, while the flagged eval calls are in generated WebAssembly glue that builds embedded functions.
- Credential-related paths such as .npmrc and agent auth files are listed as protected local paths.
- Hook context uses git to derive a repository fingerprint and sends project identity data to the configured Mnemonik API.
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.166.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.166.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.