registry / @mnemonik/cli / 7.139.3
@mnemonik/cli@7.139.3
Mnemonik installer and local project helper
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe package has no npm install hook, and the flagged agent locations are scanner ignore-list comments rather than settings mutations. The dynamic evaluation and network behavior inspected are consistent with bundled parser support, consent-based indexing, and integrity-checked updates; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the CLI; background indexing requires explicit setup and consent.
Impact
No unintended account changes, credential disclosure, or remote payload execution was established.
Mechanism
Indexing uses selected roots and the configured service origin. The updater verifies release integrity and a signed manifest before installation.
AI rationale
The package has no npm install hook, and the flagged agent locations are scanner ignore-list comments rather than settings mutations. The dynamic evaluation and network behavior inspected are consistent with bundled parser support, consent-based indexing, and integrity-checked updates; no concrete attack behavior was found.
Evidence
package.jsondist/bin.jsdist/router.jsdist/runtime/selfUpdate.jsdist/scanner/data.js
Network endpoints2
api.mnemonik.devregistry.npmjs.org/%40mnemonik%2Fcli/
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 install scripts and exposes the CLI through dist/bin.js.
- The eight flagged agent-integration locations are comments in scanner ignore lists; they describe preserving project rules and excluding shell snapshots or worktree artifacts, not changing agent settings.
- Background indexing is an explicit CLI action that requires consent flags and selected roots; its API uses the package’s configured service origin.
- The updater checks package integrity and a signed release manifest before installing an update.
- The reported eval call appears in an addEmAsm helper in bundled parser code; no remote-response execution path was established.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
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.3.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.139.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.