registry / @mnemonik/cli / 7.149.0
@mnemonik/cli@7.149.0
Mnemonik installer and local project helper
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package has no npm lifecycle scripts. Its first-party agent hook setup is a guarded host-install capability, so a warning is appropriate; the flagged eval is WebAssembly glue and does not establish remote code execution.
Static reason
One or more suspicious static signals were detected.
Trigger
The user invokes the CLI host installation flow.
Impact
The selected agent host configuration may be changed to install the hooks.
Mechanism
The installer handles hook components, selects a host scope, and applies installation checks.
AI rationale
The package has no npm lifecycle scripts. Its first-party agent hook setup is a guarded host-install capability, so a warning is appropriate; the flagged eval is WebAssembly glue and does not establish remote code execution.
Evidence
package.jsondist/install/hosts.js
Decision evidence
public snapshotAI called this Suspicious at 78.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest declares a first-party Claude Code hooks package as a host integration.
- The host installer handles hook installation and requires an existing installation identifier for protected integrations.
- Install defaults host setup to user scope; moving between scopes requires a migration check.
- The package has no npm lifecycle scripts, and the CLI bootstrap verifies runtime artifacts before launching them.
- The eval match is in WebAssembly glue that constructs functions from module-provided strings.
Evidence against
- No source evidence establishes unconsented or malicious host-configuration changes.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
8 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
1 Critical6 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
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
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @mnemonik/cli@7.149.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.149.0 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.