registry / @mnemonik/cli / 7.139.8
@mnemonik/cli@7.139.8
Mnemonik installer and local project helper
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe manifest has no npm lifecycle scripts or runtime dependencies, and the required agent-related locations concern scanner exclusions rather than agent configuration changes. The flagged evaluation is WebAssembly integration code, while the inspected update path verifies a signed release; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
No malicious trigger was found; the package runs through its command-line entry point or exported APIs.
Impact
No malicious effect was established.
Mechanism
The inspected code provides scanner, authentication, and update functions; the update path checks release identity and signature.
AI rationale
The manifest has no npm lifecycle scripts or runtime dependencies, and the required agent-related locations concern scanner exclusions rather than agent configuration changes. The flagged evaluation is WebAssembly integration code, while the inspected update path verifies a signed release; no concrete attack behavior was found.
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a command-line entry point and has no npm lifecycle scripts or runtime dependencies.
- The indicated locations in eight bundled files concern scanner ignore rules: they describe keeping Claude rules content searchable and suppressing worktree directories, not writing agent configuration.
- Authentication helpers send a supplied bearer token to the Mnemonik API origin; the inspected source shows no unrelated credential recipient.
- The dynamic evaluation in diagnostics.js constructs functions from WebAssembly glue strings. The updater checks package identity and verifies a signed release manifest before installing an update.
- Scanner data defines file ignore patterns, discovery locates repositories, and the picker stages only repositories marked selected.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
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.8.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.139.8 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.