qwenproxy-cli@1.4.1
High-performance OpenAI & Anthropic compatible API gateway for Qwen with multi-account rotation, interactive TUI, and resilient tool calling.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiAgent config mutation is real but only after an explicit sync command or TUI confirmation, and it matches the package's local gateway setup, including backups. There is no install hook, so this is a guarded capability warning rather than an unconsented install-time hijack.
Decision evidence
public snapshot- package.json has build, test, and prepack scripts and no preinstall, install, or postinstall hook.
- The qpx binary dispatches the sync subcommand to the sync-clients entry, which calls syncAllClients. With no client names, every detected client is selected.
- Default destinations include ~/.claude/settings.json and ~/.codex/config.toml, and an empty target list returns true for every client.
- syncCodex writes the Codex config and also the alternate ~/.codex or CODEX_HOME file. The same write is present in dist/sync-clients.js and the bundled dist/index.js used by the TUI.
- Those writes run only after qpx sync or Enter in the TUI sync view, not during npm install.
- Successful writes store backups, and qpx sync --restore restores them.
- The command points local coding clients at this package's own proxy, with host default 127.0.0.1.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to qwenproxy-cli@1.4.1.
See all versions of qwenproxy-cli for other recorded verdicts.
- Review the evidence and your use of qwenproxy-cli@1.4.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.