Where the licence value is actually published
Nine of the 15 families publish their licence in the repository, usually as a file or a badge. Six publish it as a tag on a model card. The two places are edited at different rates and by different processes. As of 2026-09-12.
| Item | What is published | Detail |
|---|---|---|
| Stated in the repository | Nine families | Apache 2.0 five times, MIT twice, a split by model size, and one family with an unreleased version |
| Stated on a model card | Six families | apache-2.0, tencent-hunyuan-community, skywork-license, stable-video-diffusion-community, stabilityai-ai-community and a vendor open licence |
| The same tag in both places | One family | MIT, on the repository and the card |
| Commercial use addressed elsewhere | One family | The card points at a separate page |
| No licence to state | One case | A version sold by the second with no published weights |
Inclusion rule. One row per place a licence value lives. The unreleased version keeps a row, because having nothing to license is a finding rather than a gap. Order. From the place most families use to the case where no licence exists.
1A model-card tag is easier to change than a file
A licence file in a repository moves through a commit that leaves a record. A metadata tag on a card can be edited in place, and the previous value may not be visible afterwards.
That is why every row in this register carries the date it was read. The value is a fact about a day rather than a permanent property, and the entry links the live page rather than mirroring its text.
2The file list matters as much as the licence
A repository with a standard licence and no additional notice is a different object from one that has both, and the two look identical from a distance. An acceptable-use policy beside a permissive licence adds restrictions the name does not carry.
This register records the licence name because that is the published value in that field. It does not claim the name is the complete set of conditions.
3One row has nothing to publish
In one family the version a hosted service bills per second has no published weights, so there is no licence attached to it anywhere. That is recorded as no weights published rather than left blank.
The earlier releases in that family are permissively licensed, and a sentence saying the family is open is true and will be quoted at the wrong moment. Which numbered releases are open is the answer that survives a decision.
- LicenceApache 2.0stated in the repository
- Licencemit, the same tag on the repository and on the model cardstated in the repository
- Licencetencent-hunyuan-community, a vendor-written licence rather than a standard permissive oneshown on the model card
- Licenceskywork-licensethe tag on the vendor's model card
- Licencestable-video-diffusion-community, with commercial use directed to a separate licence pagethe tag on the model card
4Sources
Repository statements and hosted rates are linked from the model pages and the how read page, checked 2026-09-12. Hardware figures are set out on requirements. Nearby: More than one card, Empty cells, Two kinds of open.