qwenproxy-cli@1.5.3
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 cloud metadata reference is part of remote URL blocking, while the flagged shell calls support browser setup and interactive clipboard use. Account credentials remain in the reviewed Qwen session flows, and Codex configuration changes occur through the explicit sync command; no concrete attack behavior was identified.
Decision evidence
public snapshot- The manifest defines a CLI and build scripts; the inspected manifest has no install lifecycle hook.
- Cloud metadata hostnames appear in remote-media URL blocking logic. The browser installer invokes Playwright’s Chromium install command.
- Codex synchronization runs through an explicit sync command and writes the caller’s API key and proxy URL into the QwenProxy provider configuration.
- Inspected session code handles browser cookies and login or refresh through Qwen account flows; the reviewed callers do not show transfer to an unrelated recipient.
- Prepared dependency source excerpts show an OSS client, input/configuration helpers, and a SQLite entry point consistent with declared package use.
- Clipboard reads are used by interactive paste handlers; the delete-chats command invokes its named account cleanup operation.
Source & flagged code
9 flaggedFindings
Affected versions and remediation
This report applies to qwenproxy-cli@1.5.3.
See all versions of qwenproxy-cli for other recorded verdicts.
- Review the evidence and your use of qwenproxy-cli@1.5.3 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.