registry / @mnemonik/cli / 7.148.0
@mnemonik/cli@7.148.0
Mnemonik installer and local project helper
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package declares no npm lifecycle scripts, and its bootstrap validates package contents before execution. Static evaluation and network signals are explained by bundled parser, update and user-invoked diagnostics functionality; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the CLI; diagnostics upload requires the preview or send command.
Impact
No confirmed attack surface was established from the inspected source.
Mechanism
The bootstrap validates package identity, version and integrity before launching. The flagged evaluation builds a function from parser module data.
AI rationale
The package declares no npm lifecycle scripts, and its bootstrap validates package contents before execution. Static evaluation and network signals are explained by bundled parser, update and user-invoked diagnostics functionality; no concrete attack behavior was found.
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 exposes a CLI entry point but declares no npm lifecycle scripts or runtime dependencies.
- The bootstrap checks package identity, version and integrity, and rejects packages with preinstall, install or postinstall hooks before launching a runtime.
- The flagged evaluation is in bundled parser code that builds a function from parser module data; the updater checks release metadata and integrity, and a separate signer verifies signatures.
- Diagnostics transfer is exposed through a preview or send command and requires a bundle identifier; no automatic install-time transfer was identified.
Evidence against
- The bundles contain evaluation, network and child-process operations, but the inspected source places them in parser, update, installer and diagnostics functionality rather than an automatic lifecycle hook.
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.148.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.148.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.