Ethical Stack.

Qwen Code

Open-source terminal coding agent optimized for Qwen models, with API-compatible and OAuth provider options.

Score calculation

(3 + 8 + 6 + 7) ÷ 4 = 6.0

4 of six dimensions rated. Unrated dimensions are excluded from the average.

Full scoring method ↗
Setup details

Qwen Code CLI client; prompts go to the selected Qwen OAuth or compatible model/API backend.

What fits your needs

Locally installed coding agent with OAuth or compatible API inference route.

Developer workflow

Qwen Code offers interactive and headless terminal use and documented IDE integrations.

See the evidence
Tradeoffs to expect

Cloud model route

OAuth or API inference can send project context to the selected provider; local client code does not keep inference local.

See the evidence
How to switch

Install and configure

Install the official CLI, then select Qwen OAuth or configure a compatible API provider.

See the evidence
Practical questions

Confirm provider

Before sending source code, check the active model, API endpoint, account terms and any IDE or agent integration.

See the evidence

Energy practices

3/10↑

For the Qwen Code CLI; the selected OAuth/API provider determines inference hosting boundary, public documentation establishes the service or route but not its request-level physical footprint. Qwen Code documents model selection, fast-model configuration and output-token generation settings. These give users workload choices; the docs do not measure energy saved. Electricity sourcing is not mapped to this route.

See the evidence

This practices/transparency assessment covers the Qwen Code CLI; the selected OAuth/API provider determines inference hosting boundary. The sources establish how the service or endpoint is exposed and provide the request controls described in the demand component; they do not give a measured per-request energy, emissions or water value. The disclosure point reflects the stated operating boundary, not a product footprint, and company-wide electricity reporting is not attributed to this route.

1 + 1 reporting + 0 electricity + 1 controls = 3/10. This grades documented practices and transparency.

The reviewed sources don’t confirm request-level electricity, emissions or water; the actual serving facility and its power mix are also not mapped to Qwen Code CLI; the selected OAuth/API provider determines inference hosting.

Reporting1/3
The reviewed documentation defines the Qwen Code CLI; the selected OAuth/API provider determines inference hosting boundary. It gives an operating-scope description, not a dated quantitative energy, carbon or water report for this route.
Electricity sourcing0/3
No reviewed source maps Qwen Code CLI; the selected OAuth/API provider determines inference hosting to a disclosed electricity mix or time-and-location-matched clean-power supply. The route's actual electricity use and emissions therefore remain unestablished.
Resource controls1/3
Qwen Code documents model selection, fast-model configuration and output-token generation settings. These give users workload choices; the docs do not measure energy saved.

Water disclosure

Water reporting has not been assessed for this choice.

Training data

—Depends on the model↑

Qwen Code supports multiple provider protocols, so the model and training-data rights depend on the backend/model release.

See the evidence

User prompts, model-improvement settings, and the original training data are different evidence questions. The reviewed product documentation does not identify a fixed model version and complete training-data rights record for Qwen Code CLI client; prompts go to the selected Qwen OAuth or compatible model/API backend., so this assessment remains unscored.

Exact model selection, release version, source inventory, permissions, post-training data, and creator-remedy scope remain unresolved.

Your data & privacy

—Not enough evidence↑

Qwen Code runs as a local terminal client, but model inference is routed to the provider selected in its configuration or sign-in flow.

See the evidence

The official product page describes OAuth and OpenAI/Anthropic/Gemini-compatible APIs. Local installation therefore doesn’t show local inference or one privacy route. Qwen Studio terms cannot be assumed to govern every third-party-compatible endpoint.

The actual backend, model, account, prompt retention and training settings depend on the selected OAuth or API route.

Openness

8/10↑

The Qwen Code project publishes an open-source terminal agent and SDK; model and provider licenses are separate.

See the evidence

The official repository and product documentation present Qwen Code as open source with terminal, headless, IDE, and SDK workflows. This supports code inspectability, not an assumption that every connected model, host, or account is open.

The score reflects service-level inspectability and control, not usefulness or model quality.

Verify the repository license and selected provider/model license independently.

Worker protections

6/10↑

Alibaba publishes group workforce indicators, an Employee Rights Code, employee reporting channels and compliance processes; these describe Alibaba employees, not the AI data-labeling supply chain.

See the evidence

Alibaba’s ESG employee-development pages report workforce composition and employee participation indicators, while its integrity and governance pages describe code compliance, reporting channels, compliance processes, and board oversight. These are concrete group-level employee systems, but public detail on annotation, evaluation, content moderation, and infrastructure contractor conditions or outcomes remains limited. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

1 + 2 pay & conditions + 2 worker voice & remedy + 1 evidence & follow-through = 6/10. This grades documented worker safeguards, not a measured rate of mistreatment.

The reviewed pages don’t show AI-data subcontractor coverage, worker-level wage/hour outcomes, case counts or remediation outcomes for labor reports, or independent labor-audit results.

Pay & conditions2/3
Company ESG disclosures report workforce composition and employee participation indicators and describe employee-rights standards; this is concrete employee evidence but does not demonstrate coverage of AI data work or contractors.
Worker voice & remedy2/3
Alibaba describes employee reporting and escalation channels, privacy/non-retaliation protections, and dedicated compliance processes; public labor-specific case outcomes were not located.
Evidence & follow-through1/3
Governance materials describe compliance training and audit/control processes, but the reviewed public disclosures do not provide independent worker-level labor assurance or remediation results.
Workers rubric ↗

Military ties

7/10Not established↑

Qwen3.8’s released model licenses don’t spell out a military-use ban. Alibaba publishes stronger rules for its separate QwenWork hosted service; no Qwen3.8 military contract was established.

See the evidence

The Qwen3.8-27B release uses Apache 2.0, while the larger Qwen3.8 release has its own license. Neither reviewed release license carries the QwenWork hosted-service military restrictions. QwenWork prohibits specified weapons and military end uses and permits service enforcement, but that separate contract doesn’t spell out controls on downloaded Qwen3.8 weights. No Alibaba military contract or Qwen3.8 deployment was established in this bounded source review. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

7 base + 0 safeguard adjustment = 7/10 (1 of 9 safeguard points; every 3 adds 1). No military relationship was established in the cited sources. This ranks above known defense ties without claiming a verified clean record.

The reviewed QwenWork contract doesn’t show an Alibaba defense relationship or a companywide model restriction. Self-hosted Qwen3.8-27B and Qwen3.8-Max use separate licenses; undisclosed contracts, deployments, and enforcement outcomes remain unknown.

Use restrictions0/4
The reviewed Qwen3.8 release licenses do not impose a specific military-purpose ban. Restrictions in the separate QwenWork customer contract are not applied to these weights.
Enforcement & oversight0/3
Hosted-service suspension rights don’t show monitoring or enforcement over downloaded Qwen3.8 copies. No release-specific military oversight was established.
Relationship disclosure1/2
Alibaba publishes the release licenses and a separate hosted military-use policy, making the scope distinction inspectable. No military customer or deployment record is established.

The QwenWork hosted-service terms include product-specific use safeguards, but no Alibaba defense contract or military deployment was established in reviewed materials. Its Qwen3.8 model repositories have distinct licenses, so the QwenWork safeguards are not attributed to self-hosted weights or treated as evidence of a military relationship.

Military rubric ↗

BDS targets

Not listed↑

We did not find Alibaba Cloud / Qwen team among the named targets in the two official BNC campaign lists. This is a limited list check, not BDS approval.

See the evidence

Alibaba Cloud / Qwen team is not a named target in the checked lists, but BDS uses selective campaigns, so absence cannot establish a clean record. Running downloaded weights locally is a different decision from paying the developer or a cloud host; check the host as well. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

This review covers the named targets in the BNC consumer/pressure guide and No Tech campaign, not every BDS campaign, local group, investment or supplier. Lists and ownership can change. A company’s absence from these lists is not an endorsement or proof that it has no relevant relationships.

More from Alibaba

All sources

Side by side