registry / @mnemonik/cli / 7.173.2
@mnemonik/cli@7.173.2
Mnemonik installer and local project helper
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install hooks, and the CLI bootstrap runs on invocation. The flagged dynamic evaluation is in generated WebAssembly support, while the inspected hook helper gathers local repository context without exposing credential values.
Static reason
One or more suspicious static signals were detected.
Trigger
User invokes the mnemonik CLI or calls exported package functionality.
Impact
The inspected source does not establish automatic collection or disclosure of credentials, unrelated remote execution, or other malicious behavior.
Mechanism
The CLI bootstraps its installer when invoked; scanner code includes generated WebAssembly glue, and hook-support code can derive project context and post it to a supplied server.
AI rationale
The manifest has no install hooks, and the CLI bootstrap runs on invocation. The flagged dynamic evaluation is in generated WebAssembly support, while the inspected hook helper gathers local repository context without exposing credential values.
Network endpoints1
github.com
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no install or lifecycle scripts and declares no runtime dependencies.
- The CLI calls bootstrap only when invoked; importing the package exports modules without invoking the CLI entry point.
- The scanner's eval calls construct functions from embedded WebAssembly module exports, rather than evaluating a remote response.
- The hook helper runs git locally to derive repository context; the inspected code does not show credential values being sent.
Evidence against
- The package includes network and process-execution code for its installer and runtime features.
- A hook helper posts a bearer token and project context to a server value supplied to the helper.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
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.173.2.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.173.2 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.