registry / @mnemonik/cli / 7.146.7
@mnemonik/cli@7.146.7
Mnemonik installer and local project helper
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and source inspection found no concrete attack behavior. The flagged dynamic evaluation is part of bundled parser runtime code; the updater verifies its release inputs before installation.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI entrypoint runs when a user invokes the command; no install-time trigger is configured.
Impact
No malicious impact was established from the inspected source.
Mechanism
The updater retrieves release metadata and checks signatures and package integrity before installing a release. The flagged eval helper appears in bundled parser runtime code.
AI rationale
The manifest has no lifecycle scripts, and source inspection found no concrete attack behavior. The flagged dynamic evaluation is part of bundled parser runtime code; the updater verifies its release inputs before installation.
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no lifecycle scripts or runtime dependencies; the CLI runs through its declared bin entrypoint.
- The updater checks a signed release manifest and verifies the package integrity before installing a runtime.
- The flagged eval sites are in an addEmAsm helper in bundled parser runtime code, not a remote-response execution path.
- The required runtime, installer, authentication, project, and scanner files were inspected; their cited excerpts show product setup and helper behavior without establishing an attack.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
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.146.7.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.146.7 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.