Get the weekly 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. No account.
The document states that for model repositories created after August 2024, the Hub no longer automatically infers the library type as Transformers when a config.json file is present, requiring contributors to declare library_name explicitly in model card metadata.
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
This provision introduces an operational breaking change for contributors who relied on implicit Transformers detection; repositories created after August 2024 without an explicit library_name declaration will not be correctly classified, affecting widget display, API routing, and discoverability filters.
Establishes a breaking change requirement for new model repositories, mandating explicit library specification rather than relying on automatic detection.
View full change record →This provision establishes that model repositories created after August 2024 must include an explicit library_name declaration in metadata; repositories lacking this field will not be automatically assigned the Transformers library classification, which affects how models are displayed and accessed through Hub interfaces and APIs.
Cross-platform context
See how other platforms handle August 2024 Library Auto-Detection Removal and similar clauses.
Compare across platforms →Monitoring
Hugging Face has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"For model repos created after August 2024, this is not the case anymore, so you need to set library_name: transformers explicitly.Excerpt from Hugging Face's Model Card Guidelines
1) REGULATORY LANDSCAPE: This provision is a platform operational change with no direct regulatory implications. It does not engage specific regulatory frameworks. 2) GOVERNANCE EXPOSURE: Medium. Organizations maintaining large numbers of Hub model repositories created after August 2024 may face discoverability and functional issues if library_name is not explicitly set. This creates an operational audit requirement for repository maintainers. 3) JURISDICTION FLAGS: No jurisdiction-specific exposure identified for this provision. 4) CONTRACT AND VENDOR IMPLICATIONS: Organizations that have integrated Hub model APIs into downstream pipelines should verify that repositories created after August 2024 have correct library_name declarations to ensure uninterrupted widget and API functionality. This is a platform-side operational change that may require updates to automated model upload workflows. 5) COMPLIANCE CONSIDERATIONS: Teams maintaining automated model publication pipelines should audit their upload scripts to confirm explicit library_name inclusion. Organizations with model governance inventories should verify that newly created repositories are correctly classified in both Hub metadata and internal records.
This provision introduces an operational breaking change for contributors who relied on implicit Transformers detection; repositories created after August 2024 without an explicit library_name declaration will not be correctly classified, affecting widget display, API routing, and discoverability filters.
This provision establishes that model repositories created after August 2024 must include an explicit library_name declaration in metadata; repositories lacking this field will not be automatically assigned the Transformers library classification, which affects how models are displayed and accessed through Hub interfaces and APIs.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Hugging Face.