registry / @mnemonik/cli / 7.154.0
@mnemonik/cli@7.154.0
Mnemonik installer and local project helper
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe inspected source does not establish an active attack: the manifest has no lifecycle scripts, the flagged evaluation is generated WebAssembly glue, and the token helper’s package callers and credential origin were not shown. The static signals therefore do not support a malicious verdict.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI or invoking its exported package API.
Impact
No confirmed malicious impact was established.
Mechanism
The static evaluation signal is in WebAssembly glue; the hook request helper posts to its supplied server, but no package caller for that helper was found.
AI rationale
The inspected source does not establish an active attack: the manifest has no lifecycle scripts, the flagged evaluation is generated WebAssembly glue, and the token helper’s package callers and credential origin were not shown. The static signals therefore do not support a malicious verdict.
Decision evidence
public snapshotAI called this Clean at 74.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- The manifest maps the CLI and package exports to local files; its inspected metadata declares no lifecycle scripts or runtime dependencies.
- The flagged evaluation call is in generated WebAssembly glue that builds a function from module-provided assembly text.
- The hook helper sends a caller-provided token and body to a caller-provided server; package-wide search found no other references to that helper, so the inspected source does not establish credential forwarding to an unrestricted recipient.
- The inspected install journey uses the Mnemonik API origin by default, and the credential cleanup path removes stored entries.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
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 · L9235257var func = `(${args}) => { ${body} };`;
L5258: ASM_CONSTS[start] = eval(func);
L5259: }
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.154.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.154.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.