Model cards & licenses
Read a repository responsibly: intended use, access restrictions, evaluation claims, and licensing.
6 sections / hugpad handbook
On this page
What is a model card?
A model card is the repository’s README on Hugging Face. Authors may describe the model architecture, training data, intended use, evaluation results, example code, and known limitations. The level of detail varies by repository.
hugpad displays the available card rather than substituting a generic description. Treat author-reported claims as claims from that source; inclusion in the directory is not independent validation.
What to check before use
- Whether the model supports your task, language, modality, and required input/output formats.
- Hardware and software requirements, dependencies, quantization variants, and the recommended loading method.
- Evaluation setup: benchmarks, comparison conditions, and limitations of the reported results.
- Safety considerations, known failure modes, and whether the model is suitable for your intended context.
- License text for the weights, code, and any referenced datasets. These may have different permissions.
Licenses are repository-specific
A license tag helps identify a license, but the repository’s actual terms govern use. Do not assume public availability means unrestricted commercial use, redistribution, or permission to rebrand the model.
If a license is missing, hugpad does not infer permission. Visit the repository, read its license and notices, and contact the publisher when terms are unclear. See Hugging Face’s license documentation.
Public, gated, and private models
| Access | What to expect |
|---|---|
| Public | Repository metadata may be discoverable without signing in. Individual files and terms still require review. |
| Gated | The author may require an access request and acceptance of conditions on Hugging Face before downloading files. |
| Private | A repository may not appear in hugpad’s public directory or launch selector. This is not a private-repository browser. |
Tokens do not change model terms
Separate assets, separate permissions
