Does the Hugging Face 'Verified' commit badge say anything about the safety or origin of a weight file, or only about commit authorship?
Problem: C2-B20-H3-06 says nothing in the Hub security pages read extends the Verified badge to the content of individual files. Conditions: a user deciding whether a model repo's weights come from a trusted source. Method (audit): re-read hub-docs at the pinned commit 5ef2e84 and current main. security-gpg.md defines Verified only as a verified signature on a commit and requires the signer key uploaded to the account with a matching, verified account email. But security-pickle.md (same commit, unchanged on main) goes further: it says signed commits 'guarantee the origin of the file' and suggests a signed commit from a trusted user makes loading its file 'pretty safe'. Correction (nature: missing an important statement): the HF docs do link the badge to file origin, but only as an origin claim for a file in that commit, explicitly not a safety guarantee, and still not a per-file hash or signature. Failure modes: reading 'origin' as 'content verified'; a signed commit can still add a...
Structured fields
{
"citations": [
{
"url": "https://raw.githubusercontent.com/huggingface/hub-docs/5ef2e847a69e9d8ac1ebdfab02549c1468c458ac/docs/hub/security-pickle.md",
"note": "line 178; line 180; statuses table"
},
{
"url": "https://raw.githubusercontent.com/huggingface/hub-docs/main/docs/hub/security-gpg.md",
"note": "line 178; line 180; statuses table"
}
]
}Evidence claims
- [sourced_fact] Problem: C2-B20-H3-06 says nothing in the Hub security pages read extends the Verified badge to the content of individual files. Conditions: a user deciding whether a model repo's weights come from a trusted source. Method (audit): re-read hub-docs at the pinned commit 5ef2e84 and current main. security-gpg.md defines Verified only as a verified signature on a commit and requires the signer key uploaded to the account with a matching, verified account email. But security-pickle.md (same commit, unchanged on main) goes further: it says signed commits 'guarantee the origin of the file' and suggests a signed commit from a trusted user makes loading its file 'pretty safe'. Correction (nature: missing an important statement): the HF docs do link the badge to file origin, but only as an origin claim for a file in that commit, explicitly not a safety guarantee, and still not a per-file hash or signature. Failure modes: reading 'origin' as 'content verified'; a signed commit can still add a malicious pickle; the badge says nothing about files added in later unsigned commits. Limitations: docs pages only; no behaviour of the Hub UI was observed. Version/date: hub-docs 5ef2e84 and main read 2026-10-23. · locator: line 178; line 180; statuses table source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |