registry / @mnemonik/cli / 7.141.1
@mnemonik/cli@7.141.1
Mnemonik installer and local project helper
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install hook, and the reviewed scanner, WebAssembly, authentication, and update paths did not establish concrete attack behavior. The scanner locations concern scoped indexing, while the update path verifies signed release data.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The package has no npm lifecycle scripts; its installer and updater run through explicit CLI commands.
Impact
The inspected behavior establishes no unconsented credential disclosure, remote code execution, or broad agent configuration change.
Mechanism
The inspected scanner locations define scoped indexing exclusions. The CLI update command checks the release digest and signed manifest before installing an update.
AI rationale
The manifest has no install hook, and the reviewed scanner, WebAssembly, authentication, and update paths did not establish concrete attack behavior. The scanner locations concern scoped indexing, while the update path verifies signed release data.
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares no npm lifecycle scripts; it exposes dist entrypoints for the CLI and library.
- The flagged scanner locations describe scoped indexing exclusions: `.claude/rules.md` remains indexable, while `.claude/worktrees/` is suppressed.
- The repeated eval locations are in the embedded WebAssembly loader, where it builds JavaScript bindings for module exports.
- The CLI updater checks release integrity and a signed release manifest; the signer code verifies signatures, and the router calls the updater for the `update` command.
- The inspected required module excerpts show local auth, parser, transport, and generated bundler code; they establish no separate install-time attack behavior.
Evidence against
- The package has network and update functionality, but the inspected updater verifies the release manifest and integrity before installation.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystem
Source & flagged code
9 flaggeddist/diagnostics.jsView file
923import { createHash, createPublicKey, randomUUID, timingSafeEqual, verify as verifySignature } from "node:crypto";
L924: import { execFile, execFileSync } from "node:child_process";
L925: function windowsCommand(file) {
High
Child Process
Package source references child process execution.
dist/diagnostics.jsView on unpkg · L9235245var func = `(${args}) => { ${body} };`;
L5246: ASM_CONSTS[start] = eval(func);
L5247: }
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
2 Critical6 High4 Medium4 Low
CriticalRemote Response Code Executiondist/runtime/selfUpdate.js
CriticalPrevious Version Dangerous Deltadist/runtime/signers.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
Affected versions and remediation
This report applies to @mnemonik/cli@7.141.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.141.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.