registry / @mnemonik/cli / 7.170.5
@mnemonik/cli@7.170.5
Mnemonik installer and local project helper
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install hooks, and the CLI bootstraps only when invoked. The flagged eval constructs functions for generated WebAssembly glue; the inspected hook context gathers local project identity and hashes rather than forwarding raw credentials or environment values.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI behavior runs when a user invokes the command; the package has no install lifecycle scripts.
Impact
No malicious behavior was identified in the inspected source.
Mechanism
The scanner evaluates generated WebAssembly glue functions, and hook context code derives project hashes and Git repository fingerprints for the package’s service.
AI rationale
The manifest has no install hooks, and the CLI bootstraps only when invoked. The flagged eval constructs functions for generated WebAssembly glue; the inspected hook context gathers local project identity and hashes rather than forwarding raw credentials or environment values.
Network endpoints1
api.mnemonik.dev
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 describes an installer and local project helper, exposes a CLI and library entry point, and has no lifecycle scripts.
- The CLI runs bootstrap only when invoked; its help path prints help without bootstrapping.
- The scanner’s eval builds functions from WebAssembly module strings for Emscripten glue code.
- The hook context collects project identity and Git remote data, then computes a keyed hash for the project root; it does not put raw environment values in that context payload.
- The installer uses api.mnemonik.dev as its default API origin, with an environment variable to configure it.
Evidence against
- The scanner uses eval, but the surrounding code identifies this as generated WebAssembly glue rather than concealed remote code execution.
- The hook context reads selected environment values for a local Git subprocess, but the inspected payload contains project context and hashes rather than those values.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
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.170.5.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.170.5 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.