qwenproxy-cli@1.5.0
High-performance OpenAI & Anthropic compatible API gateway for Qwen with multi-account rotation, interactive TUI, and resilient tool calling.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest has no npm install hook, and the flagged shell use is part of TUI clipboard handling. Account and client configuration behavior is tied to Qwen requests or explicit CLI commands; source inspection did not establish a concrete attack.
Decision evidence
public snapshot- The manifest declares no npm install hook. The launcher reaches the updater only for the explicit update command.
- The flagged clipboard read is used by TUI paste handling; it is not sent to a remote service.
- Codex configuration writes occur in the client sync flow, which is exposed as an explicit CLI command with restore options.
- Login and session code sends credentials to Qwen authentication endpoints and keeps cookies in account-scoped caches for Qwen requests.
- The chat deletion routine is exposed through the explicit purge command and operates on configured Qwen accounts.
- The inspected dependency manifests and source describe HTTP serving, object storage, and SQLite behavior; their scripts show no install hook.
- The scanner’s shell and network signals correspond to clipboard support, browser setup, and the explicitly invoked updater; source inspection did not establish unrelated collection or hidden destructive behavior.
Source & flagged code
9 flaggedFindings
Affected versions and remediation
This report applies to qwenproxy-cli@1.5.0.
See all versions of qwenproxy-cli for other recorded verdicts.
- Review the evidence and your use of qwenproxy-cli@1.5.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.