Ethical Stack.

Qwen3-Coder-Next

Coding-agent model with 80B total and 3B active parameters, native 256K context, and tool-use/recovery training; published for local development and common coding harnesses.

Score calculation

(2 + 3 + 7 + 6 + 7) ÷ 5 = 5.0

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

Full scoring method ↗
Setup details

Qwen3-Coder-Next base/instruct and official precision variants, a distinct coding-agent family from general Qwen3.8.

What fits your needs

Qwen3-Coder-Next base/instruct and official precision variants, a distinct coding-agent family from general Qwen3.8.

Good fit

Coding-agent model with 80B total and 3B active parameters, native 256K context, and tool-use/recovery training; published for local development and common coding harnesses.

See the evidence
Tradeoffs to expect

Tradeoffs

Apache 2.0 is listed for Qwen3-Coder-Next; confirm derived or quantized checkpoint terms separately. Apache-licensed weights and technical details are public, with multiple officially maintained checkpoints. Training-data provenance and end-to-end recipe remain partial, separate from the weights license.

See the evidence
How to switch

Local setup

At 80B total parameters, it is not a general consumer-laptop model despite only 3B active per token. Use official model/runtime guidance and size total weights, context, and KV cache.

See the evidence
Practical questions

Weights and license

Fetch the exact checkpoint revision and read its own license; sibling and distilled variants may inherit different terms.

See the evidence

Hardware

At 80B total parameters, it is not a general consumer-laptop model despite only 3B active per token. Use official model/runtime guidance and size total weights, context, and KV cache.

See the evidence

Training data

Treat the weight license and public web/data availability separately from evidence of permission for the training data.

See the evidence

Energy practices

2/10↑

This is a practices and disclosure score for the named release, not a request-level energy or emissions estimate.

See the evidence

The Coder-Next card provides a local serving path but no energy, emissions, water, or quantified training-power data. This score rewards a stated operating boundary; it does not infer impact from missing measurements.

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

No per-request electricity, emissions, water, serving mix, or independently reviewed footprint is established in the cited sources.

Reporting1/3
The official release materials provide downloadable weights and a local serving path for Qwen3-Coder-Next; this establishes an operating boundary, not a measured footprint.
Electricity sourcing0/3
No model-specific clean-electricity sourcing or hourly power evidence is published in the reviewed sources; zero means unestablished, not dirty electricity.
Resource controls0/3
No model-specific documented control or measured physical resource reduction is established by the reviewed release materials. Public weights or smaller variants alone do not prove reduced resource use.

Water disclosure

Water reporting has not been assessed for this choice.

Training data

3/10↑

The release provides some training-process information, but not a complete permission ledger for inherited and later training data.

See the evidence

The model card describes the training stages and data foundation at a high level, but the reviewed sources do not provide a complete named dataset and permission ledger. A public weight license governs use of those weights; it is not proof that every training source was permitted.

1 base + 1 source transparency + 1 documented permission + 0 creator controls = 3/10. Weight licensing is not treated as training data permission.

Complete source lists, source-specific rights, inherited-base provenance, synthetic-data generation permissions, and creator removal or retraining remedies remain unestablished.

Source transparency1/3
The model card describes the training stages and data foundation at a high level, but the reviewed sources do not provide a complete named dataset and permission ledger.
Documented permission1/4
Some named or permissively licensed material is described, but the sources don’t settle permission for the full inherited and later-stage training data.
Creator controls0/2
The reviewed model documentation doesn’t show creator permission covering all training data, opt-out, removal, or retraining remedy for this model family.
Data-rights rubric ↗

Your data & privacy

—Not enough evidence↑

Privacy depends on where these released weights are run; the model family has no single prompt-retention or training route.

See the evidence

The official release makes weights available for separate deployments, but it does not define one inference host or retention policy for every user. Local and hosted operators may handle prompts differently, so a single numerical privacy grade would misstate this model-level entry.

The user-selected host, region, telemetry, logging, extensions, and provider training terms are outside the checkpoint release and require a route-specific review.

Openness

7/10↑

Apache-licensed weights and technical details are public, with multiple officially maintained checkpoints. Training-data provenance and end-to-end recipe remain partial, separate from the weights license.

See the evidence

Apache-licensed weights and technical details are public, with multiple officially maintained checkpoints. Training-data provenance and end-to-end recipe remain partial, separate from the weights license. This openness rating concerns artifacts and reproducibility only; it does not assess whether the original training data was authorized.

Apache 2.0 is listed for Qwen3-Coder-Next; confirm derived or quantized checkpoint terms separately. Model weights and documentation are available, but limitations described above reduce source-level reproducibility.

The checked release and license apply to the named checkpoints; sibling variants, future versions, and the underlying training data may have different terms or disclosures.

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.

1 base + 2 conditions + 2 worker voice/remedy + 1 evidence/follow-through = 6/10. This grades documented safeguards, not proven 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.

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↑

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

See the evidence

The official BNC consumer boycott/pressure guide and No Tech campaign page do not name Alibaba Cloud / Qwen team among their current targets. BDS uses selective campaigns, so absence from these lists is neutral and should not be read as a clean record or approval.

This check covers only named targets in the two cited BNC campaigns; it does not cover all BDS campaigns, local groups, investments, suppliers, or downstream hosts. Lists and ownership may change.

More from Alibaba

All sources

Side by side