registry / @mnemonik/cli / 7.139.0
@mnemonik/cli@7.139.0
Mnemonik installer and local project helper
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe scanner hints resolve to bundled parser and project-scanning code, not a confirmed attack chain. The manifest has no lifecycle scripts, and the reviewed updater validates signed release metadata before replacing the runtime.
Static reason
One or more suspicious static signals were detected.
Trigger
The reviewed runtime behavior is reached through CLI or API use; no automatic install trigger is declared.
Impact
No confirmed unauthorized file change, credential transfer, or remote code execution was established.
Mechanism
No malicious mechanism was established. The flagged `.claude` matches relate to project-scanner ignore patterns, and the parser evaluation builds functions from embedded parser data.
AI rationale
The scanner hints resolve to bundled parser and project-scanning code, not a confirmed attack chain. The manifest has no lifecycle scripts, and the reviewed updater validates signed release metadata before replacing the runtime.
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 CLI and import entrypoints and declares an empty scripts object, with no install lifecycle hook.
- The `.claude` matches are scanner comments about scoped project-directory handling; the scanner configuration uses ignore patterns, not agent configuration writes.
- The updater verifies a signed release manifest and matching package version and integrity before installing an update; the router calls it through the CLI update flow.
- The `eval` matches build parser functions from embedded WebAssembly parser data; the inspected source does not show remote responses reaching that sink.
- The reviewed scanner, authorization, and install-session files expose project-scanning and user-facing CLI functions; no concrete unauthorized credential transfer or account action was established.
Evidence against
- Bundled parser code contains `eval`-generated functions, and diagnostic helpers use child-process execution; inspected contexts are parser support and CLI tooling.
Behavioral surface
ChildProcessCrypto
Source & flagged code
7 flaggeddist/diagnostics.jsView file
898import { createHash, createPublicKey, randomUUID, timingSafeEqual, verify as verifySignature } from "node:crypto";
L899: import { execFile, execFileSync } from "node:child_process";
L900: function windowsCommand(file) {
High
Child Process
Package source references child process execution.
dist/diagnostics.jsView on unpkg · L8985213var func = `(${args}) => { ${body} };`;
L5214: ASM_CONSTS[start] = eval(func);
L5215: }
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 Critical5 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
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
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @mnemonik/cli@7.139.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.139.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.