registry / @mnemonik/cli / 7.156.0
@mnemonik/cli@7.156.0
Mnemonik installer and local project helper
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest has no install lifecycle scripts, and the inspected dynamic evaluation is part of WebAssembly support. The scanner hints do not establish a concrete attack, so this package is marked clean.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the CLI or invokes its scanner and installer features.
Impact
No confirmed attack impact was established.
Mechanism
The reviewed eval calls construct functions from WebAssembly module content; the inspected hook helper posts a supplied body to a supplied server.
AI rationale
The manifest has no install lifecycle scripts, and the inspected dynamic evaluation is part of WebAssembly support. The scanner hints do not establish a concrete attack, so this package is marked clean.
Decision evidence
public snapshotAI called this Clean at 72.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- package.json declares no lifecycle scripts, and the CLI entrypoint invokes the bootstrap only when run.
- The scanner’s eval builds functions from WebAssembly module exports; the same pattern appears in bundled helper code.
- The hook helper sends a caller-supplied body to a caller-supplied server. The inspected code does not establish an unrelated default recipient or an unconsented credential transfer.
- The router and status modules expose CLI-related symbols, while the scanner modules expose repository discovery, scanner setup, estimates, and selection functions.
- The runtime and install modules expose release-source, journal, transaction, ownership, launcher, scanner-control, and installation functions.
- The project and identity modules expose project eligibility, project records, and identity migration functions.
- Credential reads use the file backend, and secret deletion can use the configured OS credential backend.
Evidence against
- The scanner, installer, and diagnostics bundles contain eval, network, environment, and process APIs, but the inspected matches do not establish remote response code execution or an attack.
Source & flagged code
9 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
2 Critical6 High4 Medium4 Low
CriticalRemote Response Code Executiondist/scanner/service.js
CriticalPrevious Version Dangerous Deltadist/runtime/signers.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
Affected versions and remediation
This report applies to @mnemonik/cli@7.156.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.156.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.