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

Model Card Metadata YAML Parsing and Discoverability

Low severity Medium confidence Explicit document language Common · 273 of 352 platforms
Stay ahead of the changes
Track Hugging Face and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF
Document Record

What it is

The Hub parses YAML-formatted metadata from the top of each model's README.md file to power search, filtering, and dataset/evaluation linkage features on the platform. Metadata fields including license, language, tags, datasets, and metrics are extracted and indexed by the Hub infrastructure.

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 that metadata accuracy and completeness in model card YAML headers directly determines how a model is surfaced in Hub search and filtering, affecting discoverability and the accuracy of license and dataset attribution records visible to all downstream users and auditors.

Interpretive note: The document describes the metadata parsing system but does not specify enforcement mechanisms for inaccurate or incomplete metadata beyond discoverability effects.

Clause Stability Stable

0
Changes
3
Months Monitored
May 21, 2026
First Seen
May 22, 2026
Last Seen
This clause type exists across 1424 other provisions on other platforms.

Change history

removed Jul 21, 2026

Basic technical explanation of model card format removed, suggesting this is now assumed foundational knowledge.

View full change record →
added May 21, 2026

This provision establishes the technical format and structural requirements for model cards (YAML in README.md) and emphasizes their role in platform discoverability and filtering.

View full change record →

Consumer impact (what this means for users)

Under this framework, users searching or filtering models on the Hub rely on YAML metadata fields to assess license terms, supported languages, and training data provenance. Models with incomplete or inaccurate metadata may not appear in relevant search results or may display incorrect license or attribution information.

How other platforms handle this

Apple Medium

If your app includes in-app purchases, make sure your app description, screenshots, and previews clearly indicate whether any featured items, levels, subscriptions, etc. require additional purchases.

Tinder Medium

Consistent with applicable law, you understand and agree that Tinder may not share information with you regarding your account termination if doing so would potentially impair the safety or privacy of other users.

Skillshare Medium

within the Services, all discussion boards, groups, or other public forums available to participants are publicly visible to other participants.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
Model cards are Markdown files that accompany models and provide useful information. They are files written in Markdown — specifically, each model's README.md file. The model card metadata is a YAML block at the top of the README.md file. This metadata block provides information about the model that is used by the Hub to power search, filtering, and other features.

Excerpt from Hugging Face's Model Card Guidelines

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

(1) REGULATORY LANDSCAPE: The structured metadata disclosure mechanism described here may interact with EU AI Act transparency and technical documentation obligations for AI model publishers, particularly regarding documentation of intended use, training datasets, and evaluation …

Insight

Unlock the full institutional analysis

Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.

Applicable agencies

  • Federal Trade Commission (ftc)
    Oversees unfair or deceptive business practices and can investigate companies that mislead consumers about data collection, sharing, or use.
    Who can file: Anyone affected by the company's practices (US or international)
    What you need: Your account details, a timeline of relevant events, and a description of the specific issue
    What to expect: Complaints inform FTC enforcement priorities and investigations but do not result in individual resolution or compensation
    File a complaint →

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-013099
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-013099
Captured: 2026-05-21 05:03:11 UTC
SHA-256: 66b6b488c95d3920…
URL: https://conductatlas.com/platform/hugging-face/hugging-face-model-card-guidelines/provision/CA-P-013099/model-card-metadata-yaml-parsing-and-discoverability/
Accessed: Sept. 8, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Low
Categories

Other risks in this policy

Get the research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.

Frequently Asked Questions

What does Hugging Face's Model Card Metadata YAML Parsing and Discoverability clause do?

This provision establishes that metadata accuracy and completeness in model card YAML headers directly determines how a model is surfaced in Hub search and filtering, affecting discoverability and the accuracy of license and dataset attribution records visible to all downstream users and auditors.

How does this clause affect you?

Under this framework, users searching or filtering models on the Hub rely on YAML metadata fields to assess license terms, supported languages, and training data provenance. Models with incomplete or inaccurate metadata may not appear in relevant search results or may display incorrect license or attribution information.

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 273 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.