registry / @mnemonik/cli / 7.142.0
@mnemonik/cli@7.142.0
Mnemonik installer and local project helper
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe package has no npm lifecycle scripts, and the flagged static matches resolve to embedded WebAssembly glue, signed release updating, local permission checks, or scanner ignore patterns. Source inspection found no concrete attack behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the CLI command; the package manifest declares no install lifecycle scripts.
Impact
No malicious effect was identified.
Mechanism
The evaluation sites are embedded WebAssembly glue, the updater verifies a signed package release, and the signer process call handles local permission checks.
AI rationale
The package has no npm lifecycle scripts, and the flagged static matches resolve to embedded WebAssembly glue, signed release updating, local permission checks, or scanner ignore patterns. Source inspection found no concrete attack behavior.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares no lifecycle scripts and exposes the command-line entrypoint.
- The executable calls the CLI bootstrap when invoked with arguments.
- The flagged evaluation sites are embedded Emscripten glue that constructs functions from WebAssembly module strings.
- The updater checks that it is installing the matching package release and verifies its signed release manifest and integrity.
- The agent-integration locations are scanner ignore-pattern comments and entries, including a rule for shell snapshots.
- The process execution in the signer module parses local permission-command output for access-control checks.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
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.142.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.142.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.