registry / @mnemonik/cli / 7.152.1
@mnemonik/cli@7.152.1
Mnemonik installer and local project helper
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest has no install lifecycle scripts, and the suspicious token-bearing helper is not called by the package. The source reviewed does not establish credential theft or another concrete attack.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI runs when invoked by a user; the context-binding API is available to callers that import it.
Impact
No credential transfer to an unrelated recipient or other concrete malicious impact was established.
Mechanism
The helper can send a token to a supplied server, but source search found no invocation of that helper. Context binding instead calls the supplied post callback with project context.
AI rationale
The manifest has no install lifecycle scripts, and the suspicious token-bearing helper is not called by the package. The source reviewed does not establish credential theft or another concrete attack.
Decision evidence
public snapshotAI called this Clean at 79.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares no lifecycle scripts and no runtime dependencies.
- The bearer-token request helper has no call site in the inspected package; the separate context-binding function is exported and accepts a caller-supplied post callback.
- The reviewed runtime paths contain no evidence establishing an unrelated credential recipient or a confirmed attack.
Evidence against
- The unused request helper can POST a supplied token to a supplied server, so its implementation would need caller and configuration context before it could establish credential exposure.
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.152.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.152.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.