Provision record
Hugging Face · Hugging Face Model Card Guidelines · View original document ↗

Custom license requires name and link fields

High confidence Common · 267 of 343 platforms

Key Facts · in the document’s own words

How must a custom license be specified?
“If required, you can also specify a custom license by adding other as the license value and specifying the name and a link to the license in the metadata.”
Version CA-V-006731, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Hugging Face requires that a custom license be specified by adding 'other' as the license value and providing both a name and a link to the license in the metadata.
Stay ahead of the changes
Track Hugging Face and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

This analysis describes what Hugging Face's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

Generated by a model from the captured document; not read by a person

Both the name and the link are required fields for a custom license; omitting either would mean the custom license is not properly specified under Hugging Face's guidelines.

Consumer impact (what this means for users)

Generated by a model from the captured document; not read by a person

If you use a custom license, you must supply both its name and a link to it in the metadata alongside the 'other' license value.

How other platforms handle this

Baseten

the Receiving Party may disclose Confidential Information to the extent that such disclosure is necessary for the Receiving Party to enforce its rights under this Agreement or is required by law or by the order of a court or similar judicial or administrative body, provided that (to the extent legal...

OpenAI

Written claims concerning copyright infringement must include the following information: A physical or electronic signature...A description of the copyrighted work...A description of where the allegedly infringing material is located...

Kling AI

We do not monitor, recognize, or honor any opt-out or do not track mechanisms, including general web browser "Do Not Track" settings and/or signals or other mechanisms that provide consumers the ability to exercise choice...

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
If required, you can also specify a custom license by adding other as the license value and specifying the name and a link to the license in the metadata.

Excerpt from Hugging Face's Model Card Guidelines

Provision details

Document information
Document
Hugging Face Model Card Guidelines
Entity
Hugging Face
Tracking information
First captured by ConductAtlas
May 12, 2026
Text quoted from version
CA-V-006731, captured Sept. 11, 2026
Record ID
CA-P-064790
Document ID
CA-D-000842
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-006731)
81372a4965ee6808a6de187c5fdd1d31b0fc0b193a63f664fe05883b9e76f685
Analysis generated
July 9, 2026 06:06 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-006731, captured Sept. 11, 2026 (checked Oct. 6, 2026)
Citation Record
Entity: Hugging Face
Document: Hugging Face Model Card Guidelines
Record ID: CA-P-064790
Version: CA-V-006731
Captured: 2026-09-11 00:51:34 UTC
SHA-256: 81372a4965ee6808…
URL: https://conductatlas.com/platform/hugging-face/hugging-face-model-card-guidelines/provision/CA-P-064790/custom-license-requires-name-and-link-fields/
Accessed: Oct. 25, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does Hugging Face's Custom license requires name and link fields clause do?

Both the name and the link are required fields for a custom license; omitting either would mean the custom license is not properly specified under Hugging Face's guidelines.

How does this clause affect you?

If you use a custom license, you must supply both its name and a link to it in the metadata alongside the 'other' license value.

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 267 platforms. See the full comparison.

Is ConductAtlas affiliated with Hugging Face?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Hugging Face.