Skip to content
Hugging BayGet the app

What verified and checked mean

What do verified and checked mean for a model file?

It depends on the named check. A SHA-256 match confirms that downloaded bytes match a recorded fingerprint. It does not show that a file is safe, high quality, licensed for your use or runnable. Only a separate receipt tied to exact file bytes and a named setup can report a measured run.

A checksum fingerprints file bytes. A license sets use terms. An accepted-run receipt records a specific test outcome; these are different kinds of evidence.

Machine-readable claims and the verification policy state what each record can support. Inspect one exact file record and its hash beside its run-readiness evidence. An absent file-specific receipt means no run is established here.

Updated · Page-copy source revision 8871bab84e1cf80aea1686a944ec335078a6c036 · Source files: apps/web/lib/help-centre-content.mjs, apps/web/lib/help-centre-legacy.mjs, apps/web/lib/aeo-page.mjs · Full revision record

Key facts

Desktop app
Installed locally; each model file is a separate download with its own hash check.
Checked label
Means bytes matched a published SHA-256 on this computer; not a safety guarantee.
Fit estimate
Compares file size to memory; it is not a measured run or speed promise.
Service status
/status reports site probes; it does not diagnose your local runtime.

Evidence you can inspect (plain text)

  • /verification states what site-side checks can and cannot support.
  • Open /artifact/hf-model-baai-bge-small-en-v1-5/files for the BGE small example exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-baai-bge-small-en-v1-5 for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-baai-bge-small-en-v1-5/card.md for machine-readable source facts (not a runtime test).
  • A desktop “checked” label is a local SHA-256 match, not a malware or quality review.

Unmeasured states are stated explicitly; this page does not invent run scores or compatibility guarantees.

Which date applies to which fact

  • Committed page-copy sources:
  • Upstream model metadata: Dates on artifact records when shown; not implied by page-copy revision
  • Run receipts: Only on /evidence pages when recorded; otherwise unmeasured

Page-copy revision (Updated line above) identifies committed text sources, not upstream model edits or test outcomes.

In the desktop app, checked (sometimes shown with a checkmark) means this computer compared the file on disk to the expected SHA-256 and they matched.

  1. While a download finishes, the app hashes the file locally.
  2. When the hash matches, the row shows checked and the file can load for chat.
  3. If the hash does not match, delete the partial file and download again, or pick another file from Discover.

More

A website link can pin a specific file. The app compares that pin to the live catalog before downloading. If the live hash changed, the app stops instead of fetching the wrong bytes. That is still an integrity check, not a review of model quality or malware.

Common questions

Does checked mean the model is safe?

No. Checked means the downloaded bytes match the SHA-256 fingerprint Hugging Bay published for that file.

What is verified on the website?

The Verification page describes catalog coverage and gates. It is separate from the desktop checked label on a download.

Back to help