registry / @mnemonik/cli / 7.143.0
@mnemonik/cli@7.143.0
Mnemonik installer and local project helper
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no attack: the package has no npm lifecycle scripts, and the flagged eval calls are bundled WebAssembly glue. Updates validate signed release data, while project indexing requires user acceptance and approved roots.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the CLI; indexing additionally requires accepting indexing, specifying roots, and applying setup.
Impact
No attack impact was identified; indexing is scoped to approved project roots and uses a scanner-specific credential.
Mechanism
No malicious mechanism was established. The flagged eval calls are in bundled WebAssembly glue, and updates validate signed release metadata and integrity.
AI rationale
Source inspection found no attack: the package has no npm lifecycle scripts, and the flagged eval calls are bundled WebAssembly glue. Updates validate signed release data, while project indexing requires user acceptance and approved roots.
Network endpoints3
api.mnemonik.devregistry.npmjs.orggithub.com
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI and module entrypoints and has no npm lifecycle scripts.
- The flagged eval matches are in bundled Emscripten WebAssembly glue; the updater uses separate release-handling code.
- The updater checks package identity, a signed release manifest, and matching integrity before installing an update.
- Scanner indexing requires acceptance, selected and approved roots and exclusions, and a scanner-scoped credential for the Mnemonik API.
- The agent-related byte locations are scanner ignore-pattern comments; no unconsented agent-control mutation was identified.
Evidence against
- Static findings flag dynamic evaluation, child-process use, environment access, and network calls; inspected source ties these to WebAssembly glue, installer and scanner functions, and release updates.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
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 · L9235245var func = `(${args}) => { ${body} };`;
L5246: ASM_CONSTS[start] = eval(func);
L5247: }
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/runtime/selfUpdate.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.143.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.143.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.