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

License Metadata Field and Attribution

Medium severity Medium confidence Explicitdocumentlanguage Unique · 0 of 343 platforms
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity Hugging Face recorded 2 documented changes in the last 30 days.
Start monitoring updates
Monitor governance changes for Hugging Face Create a free account to receive the weekly governance digest and monitor one platform for governance changes.
Create free account No credit card required.
Document Record

What it is

The model card YAML metadata includes a license field that specifies the terms under which the model is released, using SPDX license identifiers or a custom license designation. This field is parsed by the Hub and displayed to users accessing the model repository.

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)

This provision establishes the mechanism through which license terms are disclosed to downstream users on the Hub, making the accuracy of the license field operationally significant for intellectual property compliance and permitted downstream use assessment.

Interpretive note: The document does not specify whether Hugging Face independently verifies that license metadata fields accurately reflect the actual license terms for hosted models, leaving accuracy assurance dependent on the model publisher.

Consumer impact (what this means for users)

Under this framework, the license field in a model's YAML metadata is the primary mechanism through which users identify permitted uses, modification rights, and attribution requirements for Hub-hosted models. Users relying on this field for license compliance should verify that the stated license accurately reflects the actual terms associated with the model and its training data.

How other platforms handle this

Klarna Low

CA resident loans made or arranged pursuant to a California Financing Law license. NMLS # 1353190.

Snapchat Ads High

Advertisers who wish to run political advertising on Snapchat must complete Snap's political advertiser authorization process, comply with applicable election advertising laws, and include required disclosures identifying the funding source of political ads.

Cash App Medium

XXII. Generative AI Terms of Use

See all platforms with this clause type →

Monitoring

Hugging Face has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.

Start Monitor free trial Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
license: This field is used to indicate the license under which the model is released. It should be a valid SPDX license identifier, or a custom license if none of the standard licenses apply.

— Excerpt from Hugging Face's Hugging Face Model Card Guidelines

ConductAtlas Analysis

Institutional analysis (Compliance & governance intelligence)

(1) REGULATORY LANDSCAPE: License disclosure accuracy engages intellectual property law applicable in the jurisdictions where models are accessed and deployed. For models trained on datasets with their own license terms, the relationship between dataset licenses and model output licenses may create additional compliance considerations not fully addressed by the Hub metadata schema alone. (2) GOVERNANCE EXPOSURE: Medium. Inaccurate or missing license fields in model card metadata may create intellectual property compliance exposure for organizations that rely on Hub metadata for license due diligence without independent verification. (3) JURISDICTION FLAGS: Organizations in jurisdictions with strong copyright and database rights protections, including EU/EEA member states, face heightened exposure where model or training dataset licenses are inaccurately described or omitted from model card metadata. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams should not rely solely on Hub license metadata for compliance assessment; independent review of underlying model and dataset license terms is advisable for models used in commercial or production contexts. (5) COMPLIANCE CONSIDERATIONS: Organizations should establish a process for verifying that license fields in model card metadata of relied-upon models match the actual license documents associated with those models, and should document this verification as part of their AI procurement due diligence.

Full compliance analysis

Regulatory citations, enforcement risk, and due diligence action items.

Track 1 platform — free Try Monitor free for 14 days

Free: track 1 platform + weekly digest. Monitor: 10 platforms + same-day alerts. No credit card required.

Provision details

Document information
Document
Hugging Face Model Card Guidelines
Entity
Hugging Face
Document last updated
May 12, 2026
Tracking information
First tracked
May 21, 2026
Last verified
May 21, 2026
Record ID
CA-P-013101
Document ID
CA-D-00842
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
66b6b488c95d3920fe9e1acec75ede720f6f4f4162de5fd0577053fc630bdcb3
Analysis generated
May 21, 2026 05:03 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Hugging Face
Document: Hugging Face Model Card Guidelines
Record ID: CA-P-013101
Captured: 2026-05-21 05:03:11 UTC
SHA-256: 66b6b488c95d3920…
URL: https://conductatlas.com/platform/hugging-face/hugging-face-model-card-guidelines/license-metadata-field-and-attribution/
Accessed: May 25, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Compliance Governance Intelligence

Need to monitor specific governance provisions?

Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Start Compliance free trial

Or start with Monitor →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does Hugging Face's License Metadata Field and Attribution clause do?

This provision establishes the mechanism through which license terms are disclosed to downstream users on the Hub, making the accuracy of the license field operationally significant for intellectual property compliance and permitted downstream use assessment.

How does this clause affect you?

Under this framework, the license field in a model's YAML metadata is the primary mechanism through which users identify permitted uses, modification rights, and attribution requirements for Hub-hosted models. Users relying on this field for license compliance should verify that the stated license accurately reflects the actual terms associated with the model and its training data.

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.