Heliast Book a discovery session
Book a discovery session

Verdicts/meta-models

meta-models /Muse-Glimmer-30B

Verdict

Held

A policy file outside the licence carries a clause that restricts use.

What would change it: evidence from the licensor, or a human ruling. A hold is not a failure.

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

What was checked

  • Licence Held

    Apache-2.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
a4e59da52a7bc87ae7251dd5545c0dd437c44b68
Date assessed
2026-09-25 BACKFILL
Upstream released
2026-08-11T19:23:35Z, 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: 1060 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: Apache-2.0 (as a licence-file). Concluded: Apache-2.0.
Evidence tier
T1 a licence file in the model repository. Sufficient for Class A.
Deviation from canonical text
Deviation found: the added-clause screen found clauses outside the licence file, in the declared sibling policy files. They are quoted under the verdict.
Added-clause screen
Run over ../policy-files/muse-glimmer-30b-usage-policy.md; 2 clauses found, quoted under the verdict.
Provenance chain
Source: huggingface.co/meta-models/Muse-Glimmer-30B. 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
Canonical text pinned and digest-verified, identifier taken from the licensor's own repository metadata, added-clause screen run over sibling policy files, provenance chain recorded. The licensor's own licence file is not compared byte for byte on this evidence path.
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
added-clause: added clause in ../policy-files/muse-glimmer-30b-usage-policy.md: an age restriction: the policy sets a minimum user age: "Muse Glimmer is not intended for individuals under the age of 18\\."
added-clause: added clause in ../policy-files/muse-glimmer-30b-usage-policy.md: a use restriction: the policy prohibits or restricts uses beyond the canonical licence: "## Prohibited Uses" 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