registry / @mnemonik/cli / 7.147.0
@mnemonik/cli@7.147.0
Mnemonik installer and local project helper
AI Security Review
scanned 11d ago · by lpm-firewall-aiStatic signals resolve to bundled parser support and ordinary CLI functions. Source inspection found no concrete attack surface, so the package is clean.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the CLI or an exported API.
Impact
No concrete unauthorized data transfer, account action, persistence, or remote code execution was established.
Mechanism
The inspected network behavior uses the Mnemonik API and package release sources; local credentials are read through the CLI credential adapter. The flagged evaluation sites are in embedded parser support.
AI rationale
Static signals resolve to bundled parser support and ordinary CLI functions. Source inspection found no concrete attack surface, so the package is clean.
Network endpoints5
api.mnemonik.devregistry.npmjs.orggithub.com/JayDeeCo-Limited/mnemonik-cli/releases/download/release-assets.githubusercontent.comobjects.githubusercontent.com
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no lifecycle scripts; dist/bin.js starts the CLI bootstrap when invoked, and dist/index.js exports the CLI API.
- Inspected installer, project, scanner, status, and update modules implement CLI functions over local state and project records; no concrete attack behavior was identified.
- Authentication reads CLI credentials from a local credential adapter, and the inspected install flow sends readiness data to the configured Mnemonik API.
- The self-updater checks package integrity against a signed release manifest; release-source code restricts network destinations to the package registry, Mnemonik API, and the project’s GitHub release assets.
- The flagged eval sites are in embedded WebAssembly parser support, not a path that executes remote JavaScript.
Evidence against
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.147.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.147.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.