A leaderboard tells you what performs. It doesn’t tell you what the license lets you do. This page adds the second axis: for each model we measure, what does its license declare? We read each model’s declared license tag and sorted the board into four tiers. Where we couldn’t read a license from a primary source, we say so rather than guess.
This is reported data, not legal advice. A tier here describes what a repo’s license tag declared on 2026-07-14 — not a conclusion about whether you may ship a given product. Every tier is an hf-metadata reading of the model’s self-declared Hugging Face tag, not a license-text read. Read the license, and consult your own counsel, before you build on any model here.
Apache-2.0 / MIT / BSD, as declared. Use, fine-tune, redistribute, commercialize — no condition worth a second thought.
Attribution, an acceptable-use policy, or a large-scale (700M-MAU) clause — conditions a business typically accepts without negotiation. Llama, Gemma, most bespoke open-weight.
Non-commercial, no-military-use, or a vendor right to amend terms — as declared. Weights may exist, but the declared terms need a deliberate yes.
No weights published; governed by the provider’s API terms of service.
License not identifiable from a primary source. Never treated as permissive.
489 models on the board, tiered by declared license. Counts are derived live from the license module — read as of 2026-07-14.
The uncomfortable results — about models we ourselves route to — are the point. Reading a license looser requires strong evidence; we don’t take a dropdown’s word for a permissive verdict. These carry a surprising or contradicted tag, and we held them at the conservative tier pending a license-text read rather than promote them.
HF tag says MIT, but the repo’s own license file adds use-based restrictions the tag can’t see. Held as unresolved pending a license-text read.
Gemma has never shipped an SPDX-permissive license. Treated as a likely uploader-error tag and held at B (Gemma Terms), not promoted.
Mistral Large has historically declared non-commercial terms. Held pending a license-text read.
Tagged MIT, but the base model’s license applies underneath — capped at B by license-stacking (the Nemotron rule, applied to distills).
We read licenses from public Hugging Face metadata — the repo’s declared license tag, not the license text. About 39% of the board we read a declared tag for. The rest are gated repos we can’t read without credentials, non-standard “other” tags that name a bespoke license without saying what it says, or proprietary API-only models with no weights to license — those keep a family-level default and are not shown as verified. A tier here reports a declared license at the coverage level we disclose. It is not legal advice and not a verdict on your right to ship.