registry / @mnemonik/cli / 7.167.3
@mnemonik/cli@7.167.3
Mnemonik installer and local project helper
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package has no install hooks, and the flagged code resolves to WebAssembly support, protected-path handling, and installer API reporting. I found no concrete malicious data flow or unrelated automatic action.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI bootstrap runs when a user invokes the command; install-session reporting occurs in the installer workflow.
Impact
No automatic collection or transfer of unrelated credentials or project data was identified.
Mechanism
The scanner loads WebAssembly, and installer reporting uses a bearer token with the Mnemonik API. The flagged .npmrc references protect that path from selection.
AI rationale
The package has no install hooks, and the flagged code resolves to WebAssembly support, protected-path handling, and installer API reporting. I found no concrete malicious data flow or unrelated automatic action.
Network endpoints3
api.mnemonik.dev/api/v1/install-sessions/current/api/v1/install-sessions/{session.id}/complete
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts; the executable is a CLI entry point.
- The CLI calls bootstrap with user-supplied arguments when invoked.
- The scanner’s eval call constructs JavaScript glue from WebAssembly memory; the Node loader reads a local file, rather than evaluating an HTTP response body.
- The .npmrc path appears in protected-path logic, not as evidence of a credential read or upload.
- Install-session reporting uses the Mnemonik API and a CLI bearer token as part of the installer 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.3.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.167.3 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.