The digest

74a4da8c9fdbcd15bd1f6d01d621410d31c6fc00986f5eb687824e7b93d7a9db  qwen2.5-0.5b-instruct-q4_k_m.gguf

That line is in sha256sum format, so it can be checked mechanically rather than by eye. Save it next to the file and let the tool do the comparison:

curl -sL https://tinymodels.co/models/qwen2-5-0-5b-instruct-gguf-q4-k-m/download -o qwen2.5-0.5b-instruct-q4_k_m.gguf
curl -s https://tinymodels.co/models/qwen2-5-0-5b-instruct-gguf-q4-k-m/checksum?format=txt -o qwen2.5-0.5b-instruct-q4_k_m.gguf.sha256
shasum -a 256 -c qwen2.5-0.5b-instruct-q4_k_m.gguf.sha256
# qwen2.5-0.5b-instruct-q4_k_m.gguf: OK

What this proves, and what it does not

This digest is the upstream repository's own LFS object id for that file, so it confirms the file you receive is genuinely the publisher's artifact, unchanged. It does not attest that the model is accurate, safe or free of surprises — only that the bytes are the bytes that were published.

Other formats

• plain sha256sum line
• JSON

Going further

Verifying a download walks through this with the commands, and explains what a matching digest does and does not prove.