Heliast Book a discovery session
Book a discovery session

Verdicts/Qwen

Qwen /Qwen3.8-Flash-Next

Verdict

Rejected
  • The licence is not one Heliast admits. Heliast admits unmodified Apache 2.0 or MIT.
  • A policy file outside the licence carries a clause that restricts use.

What would change it: a revision whose licence the policy admits, assessed as its own record.

A verdict covers licence, provenance and files. Quality and fit on your own tasks are measured by Compare.

What was checked

  • Licence Rejected

    qwen-community-1.0, from a licence file (T1).

  • Provenance Not verified

    The licensor's own repository.

  • Files Not verified

    Safetensors. The weights digest was not verified, so they are not claimed as byte-checked.

  • Export screening Not yet assessed

    No export claim is made.

Verify this verdict

Download attestation.json and check it against the published key:

python scripts/verify-verdict.py

Full record
Revision
de4b8e4d43b917e7706784d8bb445c9af86a3540
Date assessed
2026-09-25 BACKFILL
Upstream released
2026-08-27T05:03:36Z, the commit date of the assessed revision, recorded 2026-09-25. A reconstruction: this verdict was assessed before upstream release tracking began, so it is excluded from the median.
Release to verdict
Verdict latency: 690 hours from the upstream release to 00:00 UTC on the assessment date. The record is dated, not timed, so the true figure may be up to 24 hours higher.
Provenance label
the weights digest was not verified for this verdict, so the weights are not claimed as byte-checked
Licence, declared and concluded
Declared: qwen-community-1.0 (as a licence-file). Concluded: LicenseRef-qwen-community-1.0.
Evidence tier
T1 a licence file in the model repository. Sufficient for Class A.
Deviation from canonical text
The grant is understood and is outside Class A: every licence reachable in the expression must be Apache-2.0 or MIT (decision 0147), so the canonical comparison does not apply. The added-clause screen also found clauses in sibling policy files; they are quoted under the verdict.
Added-clause screen
Run over ../policy-files/qwen38-flash-next-licence-terms.txt; 6 clauses found, quoted under the verdict.
Provenance chain
Source: huggingface.co/Qwen/Qwen3.8-Flash-Next. Official licensor repository: yes.
Base lineage
Not a derivative recorded in the admission record, so no base licence obligations arise.
Base-licence obligations
None recorded: this is not a derivative, or the base's conditions were not engaged.
Contradiction triage
None recorded.
Files and integrity
safetensors; the weights digest was not verified for this verdict, so the weights are not claimed as byte-checked.
Export screen
Export screening: not yet assessed. No export claim is made. The record carries status: not_assessed, basis: null, assessed_by: null, assessed_date: null, reference: null.
Declared training data
not recorded in the admission record.
What was checked
No Class A canonical comparison applies to this identifier. The added-clause screen still ran over sibling policy files, and the provenance chain is recorded below.
Signed attestation
attestation.json: a DSSE envelope over an in-toto Statement v1, whose subject is the weights file digests and whose predicate is this record's provenance artefact. Signed with the key published at /verdicts/keys/, which states the fingerprint, the date the key came into use and how to verify the signature. Key custody: a local key on one operator host, not an HSM.
Gate findings
gate-1: licence.identifier "qwen-community-1.0" is not Class A: every licence reachable in the expression must be Apache-2.0 or MIT (decision 0147), and licence is "qwen-community-1.0" reachable (plan 4.3: a licence outside Class A is an automatic fail)
added-clause: added clause in ../policy-files/qwen38-flash-next-licence-terms.txt: a separate-licence requirement: parts of the use need a licence beyond the pinned canonical licence: "If the licensee or any of its affiliates conducts a Model as a Service or AI Work Assistant business, the licensee shall obtain a separate license from Qwen before Using the Software or its derivative works for any commercial purpose."
added-clause: added clause in ../policy-files/qwen38-flash-next-licence-terms.txt: a field-of-use restriction: the policy limits which businesses, purposes or products may use the model: "If the licensee or any of its affiliates conducts a Model as a Service or AI Work Assistant business, the licensee shall obtain a separate license from Qwen before Using the Software or its derivative works for any commercial purpose."
added-clause: added clause in ../policy-files/qwen38-flash-next-licence-terms.txt: a revenue or monthly-active-user threshold: rights or obligations change past a numeric cutoff: "If the Software (or any derivative works thereof) is Used for any of the licensee's commercial products or services that have more than 100,000,000 monthly active users or US$ 20,000,000 (or equivalent in other currencies) monthly revenue, respective model name must be prominently displayed on the user interface of such product or service; and,"
added-clause: added clause in ../policy-files/qwen38-flash-next-licence-terms.txt: a naming or attribution requirement: the policy requires the model's name, a credit or an acknowledgement to appear in the product: "If the Software (or any derivative works thereof) is Used for any of the licensee's commercial products or services that have more than 100,000,000 monthly active users or US$ 20,000,000 (or equivalent in other currencies) monthly revenue, respective model name must be prominently displayed on the user interface of such product or service; and,"
added-clause: added clause in ../policy-files/qwen38-flash-next-licence-terms.txt: a use restriction: the policy prohibits or restricts uses beyond the canonical licence: "The foregoing requirement shall not apply to the licensee's internal Use of the Software, provided that such Use does not make the Software, its outputs, or its underlying model capabilities available to any third party."
added-clause: added clause in ../policy-files/qwen38-flash-next-licence-terms.txt: a binding term: the policy makes the user agree to, warrant or consent to something the licence does not: "THE SOFTWARE AND ANY OUTPUT AND RESULTS THEREFROM ARE PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT." The gate's own words, with one term normalised; the signed attestation carries them exactly.

Running models like this in your own estate? Heliast runs the same gate inside your environment, on your policy.

Book a discovery session