Ethical Stack.

Wan 2.2

Open video-generation model family with T2V-A14B and I2V-A14B 480p/720p checkpoints plus TI2V-5B at 720p.

Score calculation

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

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

Full scoring method ↗
Setup details

Wan2.2 official open weights and inference code; model card used here is T2V-A14B. The official repository documents sibling I2V/TI2V routes.

What fits your needs

Wan2.2 official open weights and inference code; model card used here is T2V-A14B. The official repository documents sibling I2V/TI2V routes.

Text to video

T2V-A14B generates five-second clips at 480p or 720p; official repository also lists image-to-video and text-image-to-video releases.

See the evidence

Local generation

The model card provides a local download and inference path with single- and multi-GPU examples.

See the evidence

Prompt extension

Optional prompt extension can call Alibaba DashScope; it can be disabled or configured with a local Qwen route.

See the evidence
Tradeoffs to expect

Large-GPU route

The documented 720p 14B single-GPU run calls for at least 80GB VRAM; multi-GPU setup is another option.

See the evidence

External prompt service

Prompt extension can send prompts to DashScope unless disabled or replaced with local prompt extension.

See the evidence
How to switch

Run from weights

Download the T2V-A14B checkpoint and use the Wan2.2 inference repository; choose T2V or an I2V sibling checkpoint for the intended input.

See the evidence
Practical questions

Input/output route

The T2V checkpoint accepts prompts; image-to-video requires an I2V checkpoint. Prompt extension is optional and can be switched off.

See the evidence

Rights in references

Use input images and likenesses only where you have the rights and consent required for your use; the release docs make output use the deployer’s responsibility.

See the evidence

Hosted route

A hosted inference provider applies its own prompt retention, region and output-handling terms.

See the evidence

Energy practices

3/10↑

This grades disclosed operating practices, not the electricity or emissions of a particular generation.

See the evidence

The release gives limited runtime or control details but no comparable per-task footprint or electricity-source evidence. Wan provides release-specific GPU and resolution operating settings; the card’s hardware test is an inference boundary, not an energy footprint. The inference code exposes offloading and dtype conversion to lower GPU-memory demand, plus clip resolution/duration selection; no physical resource saving is measured.

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

Per-task energy, serving region, facility electricity mix, water and independent footprint review are not established in the cited release sources.

Reporting1/3
Wan provides release-specific GPU and resolution operating settings; the card’s hardware test is an inference boundary, not an energy footprint.
Electricity sourcing0/3
The release materials do not report matched regional electricity sourcing or carbon-free supply for training or inference.
Resource controls1/3
The inference code exposes offloading and dtype conversion to lower GPU-memory demand, plus clip resolution/duration selection; no physical resource saving is measured.

Water disclosure

Water reporting has not been assessed for this choice.

Training data

2/10↑

The model release does not provide a complete inspectable training-source permission record.

See the evidence

The reviewed release documentation wan2.2 states it expanded its video/image training data over wan2.1, but publishes no named-source permissions ledger. It provides no source-level permission ledger or creator remedy; a model-weight license governs downstream use, not the material used to train the model.

1 base + 1 source transparency + 0 documented permission + 0 creator controls = 2/10.

Named source inventory, source-level licenses, creator remedies, and independent verification remain unestablished for this release.

Source transparency1/3
Wan2.2 states it expanded its video/image training data over Wan2.1, but publishes no named-source permissions ledger.
Documented permission0/4
The release sources do not publish a training-source permission basis or rights ledger; the weight license doesn’t settle training-data permission.
Creator controls0/2
No training-source creator permission-before-use, opt-out, removal or retraining route is documented for this release.
Data-rights rubric ↗

Your data & privacy

—Not enough evidence↑

Privacy has no single score for these downloadable weights because handling depends on the inference host and integrations.

See the evidence

The release can be run locally, but it also appears in hosted provider routes; those operators set their own request retention, training and region terms. A cloud API, where offered, is a separate policy route and is not inherited from the local weights.

A selected host, network path, telemetry, logging, external prompt enhancement, and data retention need route-specific review.

Openness

7/10↑

Apache 2.0 weights and inference code are public, with extensive deployment examples but no full training data or compute recipe.

See the evidence

The official model card and repository provide weights, Apache 2.0 license, inference code and GPU benchmarking details. Training-source inventory and full training recipe are not provided. This rating concerns release artifacts and reproducibility, not training-data permission.

7/10 reflects permissively licensed public weights/code and runnable inference, with training data and complete training details undisclosed.

A source-level training-data manifest and complete reproducibility record are unavailable for Wan2.2.

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