registry / @mnemonik/cli / 7.139.6
@mnemonik/cli@7.139.6
Mnemonik installer and local project helper
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the reviewed scanner matches describe project-file filtering rather than agent control changes. The flagged evaluation and update behavior are consistent with local parser glue and verified package updates.
Static reason
One or more suspicious static signals were detected.
Trigger
No malicious trigger was identified; the CLI runs through its command-line entry point.
Impact
No malicious effect was established.
Mechanism
The flagged evaluation is in local WebAssembly parsing glue, and the updater validates the package release before installing it.
AI rationale
The manifest has no install lifecycle hooks, and the reviewed scanner matches describe project-file filtering rather than agent control changes. The flagged evaluation and update behavior are consistent with local parser glue and verified package updates.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no lifecycle scripts or runtime dependencies; the CLI entry point invokes its bootstrap from the command line.
- The repeated `.claude` matches describe retaining project rules for indexing and suppressing a narrow worktree path; they do not show agent configuration changes.
- The flagged `eval` calls build local helpers from WebAssembly module data in bundled tree-sitter glue.
- CLI updates use the package's npm registry release metadata and verify the release manifest and package integrity before installing.
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.139.6.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.139.6 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.