registry / @mnemonik/cli / 7.140.3
@mnemonik/cli@7.140.3
Mnemonik installer and local project helper
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no malicious behavior. The scanner’s evaluation and agent-configuration signals resolve to bundled parser glue and comments, while credential status checks and installation reporting are bounded to the package’s product flow.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI bootstrap runs when a user invokes the executable; package installation has no lifecycle hook.
Impact
No credential disclosure, unconsented agent configuration mutation, or remote code execution was established.
Mechanism
The updater verifies package integrity and a signed release manifest. The installer requires consent flags or an interactive install-and-upload choice before configuring selected hosts and reporting readiness.
AI rationale
Source inspection found no malicious behavior. The scanner’s evaluation and agent-configuration signals resolve to bundled parser glue and comments, while credential status checks and installation reporting are bounded to the package’s product flow.
Network endpoints2
registry.npmjs.org/%40mnemonik%2Fcli/api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines no install lifecycle scripts or runtime dependencies; the executable starts the CLI bootstrap when invoked.
- The flagged evaluation sites construct parser callbacks inside bundled WebAssembly glue; they are not fed by network responses.
- The updater fetches this package’s npm metadata and checks package integrity against a signed release manifest before installing an update.
- Claude and Codex helpers reduce locally stored credentials to authorization status and expiration metadata; the package does not pass those tokens to an unrelated recipient.
- The installer requires explicit consent flags in automatic mode or an interactive install-and-upload choice before configuring hosts and sending readiness data.
- The agent-related scanner matches are comments about a narrow worktree exclusion; the installer configures selected hosts in user scope.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEval
Source & flagged code
8 flaggeddist/diagnostics.jsView file
919import { createHash, createPublicKey, randomUUID, timingSafeEqual, verify as verifySignature } from "node:crypto";
L920: import { execFile, execFileSync } from "node:child_process";
L921: function windowsCommand(file) {
High
Child Process
Package source references child process execution.
dist/diagnostics.jsView on unpkg · L9195244var func = `(${args}) => { ${body} };`;
L5245: ASM_CONSTS[start] = eval(func);
L5246: }
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.140.3.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.140.3 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.