Qwen Code
Website
An open-source AI coding agent that lives in your terminal.
Is Qwen Code safe? Strong public trust posture, backed by multiple independent signals.
Compare Qwen Code
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: Qwen Code scores 89.4/100 (Grade A), ranked #29 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.4/10; 100% of recent commits are signed; no published advisory affects its latest release (@qwen-code/qwen-code, qwen-code-sdk); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →
What Qwen Code can reach, and who runs it
Checked 2026-10-09, each with its source. PUBLISHER is the company's or project's own statement, which we haven't verified; CHECKED is something we observed ourselves; IN CODE is read from the project's source code. These facts describe the product. They don't change its score.
What it can reach
- PUBLISHER Starts in Auto mode by default: a classifier model approves safe file edits and shell commands and blocks risky ones. Ask Permissions mode asks before every edit and command; YOLO approves everything.
- PUBLISHER Its Chrome extension acts inside your Chrome profile, including signed-in pages, and browser results may be sent to the configured AI provider.
Where your data goes
- PUBLISHER Which provider's terms and privacy policy apply depends on how you sign in: Qwen OAuth, Alibaba Cloud Coding Plan, Vertex AI (Google Cloud), or your own API key's provider.
- IN CODE Sends usage statistics by default: the privacy.usageStatisticsEnabled setting defaults to true. Its privacy notice describes them as anonymous and optional.
Security practice
- CHECKED The repository has a SECURITY.md; GitHub private vulnerability reporting is off.
How Qwen Code could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 5.4 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Fuzzing 0 +5.3 → 94.7 A · #1 of 77
Chain of custody
Scanners check what the code says. This traces who ships Qwen Code and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/QwenLM/qwen-code, Apache-2.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.4/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies6
All 14 Scorecard checks
Binary-Artifacts 3Branch-Protection 0CII-Best-Practices 0Code-Review 10Dangerous-Workflow 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 6SAST 7Security-Policy 10Signed-Releases 0Token-Permissions 0 -
Published packages Linked and attested
- npm @qwen-code/qwen-code Source link points back to this repo Build provenance attested
- PyPI qwen-code-sdk Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest releases checked: @qwen-code/qwen-code 0.25.0, qwen-code-sdk 0.1.0rc0. No published advisory affects it (OSV, checked 2026-10-09).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Qwen Code.
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions
- Community mentions (missing)
Verify this score yourself
Every build re-issues Qwen Code’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Qwen Code compares in Coding Agents
- #1 Cline 91.7 +2.3
- #2 Codex 90.0 +0.6
- #3 Qwen Code 89.4 this agent
- #4 Bernstein 88.9 −0.5
- #5 ECC 87.8 −1.6
Bars show each HVTrust score; the tick marks Qwen Code’s 89.4.
Where the 89.4 comes from
HVTrust dimensions vs the Coding Agents average
89.4 / 100 · 100.0% confidenceQwen Code Coding Agents average (77 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
93.0 / 100Common questions about Qwen Code
Does Qwen Code publish package provenance?
Does Qwen Code have an OpenSSF Scorecard?
Is Qwen Code actively maintained?
What license does Qwen Code use?
Are Qwen Code's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
Compare Qwen Code head-to-head
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- code
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Qwen Code?
For maintainers
HVTrust scores Qwen Code from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Public Actions
Action counts reflect activity on public repos where this agent left detectable fingerprints. Private repo usage is invisible. Counts are approximate (GitHub Search API caps at 1,000 results per query). Methodology described in the Provenance Profile spec.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/qwen-code)
<a href="https://hvtracker.net/agents/qwen-code"><img src="https://hvtracker.net/badge/qwen-code.svg" alt="HVTrust"></a>
Other agents in Coding Agents
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · GitHub Search API (fingerprint actions)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON