registry / qwenproxy-cli / 1.0.0
qwenproxy-cli@1.0.0
API compatível com OpenAI que conecta clientes ao Qwen via Playwright, com suporte a múltiplas contas, tool calling e sessões persistentes.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe suspicious primitives are consistent with a Playwright-based Qwen proxy and explicit local client setup. Source inspection found no concrete malicious chain beyond the declared browser installation.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation downloads Chromium; running the CLI starts the proxy or explicitly invokes sync.
Impact
No unrelated exfiltration, stealth persistence, or automatic foreign agent-control mutation was identified.
Mechanism
A Playwright-based local proxy forwards authenticated requests to Qwen and can configure local AI clients on request.
AI rationale
The suspicious primitives are consistent with a Playwright-based Qwen proxy and explicit local client setup. Source inspection found no concrete malicious chain beyond the declared browser installation.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The install hook downloads a Chromium browser through Patchright.
- The CLI can invoke Patchright installation with a shell-enabled child process if Chromium is absent.
- The proxy retrieves Qwen session headers, including cookies, to make authenticated upstream requests.
- An explicit sync command can modify AI-client configuration files.
Evidence against
- The install hook is limited to the browser dependency required by the declared Playwright-based proxy.
- The shell-enabled install path is only reached when a user runs the CLI and Chromium is missing.
- Observed authenticated requests target the configured Qwen service, not an unrelated collection endpoint.
- AI-client configuration changes occur only through the user-invoked sync command and point clients to a local proxy.
- No self-dependency, hidden payload, unrelated secret collection, or automatic agent-config mutation was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = patchright install chromium
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = patchright install chromium
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/qwenproxy.jsView file
16L17: import { spawn, spawnSync } from "node:child_process";
L18: import path from "node:path";
High
Findings
5 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/qwenproxy.js
HighShellbin/qwenproxy.js
HighCopied Package Dependency Bridgebin/qwenproxy.js
HighRuntime Package Installbin/qwenproxy.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowWeak Cryptosrc/core/accounts.ts
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to qwenproxy-cli@1.0.0.
See all versions of qwenproxy-cli for other recorded verdicts.
- Review the evidence and your use of qwenproxy-cli@1.0.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.