registry / @mnemonik/cli / 7.140.1
@mnemonik/cli@7.140.1
Mnemonik installer and local project helper
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks. Source inspection tied the `eval` signal to bundled WebAssembly glue and found release identity and integrity checks in the updater; the agent-related cited locations concern scanner rules rather than configuration mutation.
Static reason
One or more suspicious static signals were detected.
Trigger
CLI invocation; updates are initiated by the CLI update flow.
Impact
No confirmed attack impact.
Mechanism
The inspected update flow retrieves release metadata, checks the package identity, version, and integrity, then installs the verified release. No unconsented agent configuration change or credential transfer was established.
AI rationale
The manifest has no install lifecycle hooks. Source inspection tied the `eval` signal to bundled WebAssembly glue and found release identity and integrity checks in the updater; the agent-related cited locations concern scanner rules rather than configuration mutation.
Network endpoints1
registry.npmjs.org/%40mnemonik%2Fcli/
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines a CLI and module entrypoint but has no lifecycle scripts.
- The cited agent-related locations describe project scanning rules for `.claude/` content; they do not show agent configuration changes.
- The `eval` calls construct functions from WebAssembly module glue, and the update path validates release metadata and integrity before installation.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
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.140.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.140.1 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.