MaxJeblick

Llama 2 0B unit test

Text generation

This receipt records checks for this exact file; it does not prove safety or that it will run on your device. Read the receipt

Model details
text generationLicense: unknownSHA-256 recorded for 9 of 11 filessafetensors · BIN
Quick answer: compatibility and sources

Can I run llama2-0b-unit-test on my computer?

It depends on your memory, processor, file format and runtime. A download is not confirmed by the current file evidence; inspect the file record before trying it. A file-size fit is an estimate, not a successful run or speed promise. Read the license before use.

llama2-0b-unit-test is an open-weights language model for text generation. Model weights are learned parameters; a runtime loads them. A hosted file is an individual file Hugging Bay can serve. SHA-256 identifies exact file bytes. The availability date above applies to this file record, not the upstream metadata update date.

As of the recorded file availability check on .

Recorded SHA-256 for model.safetensors: 5108f9b61c4c32b2ae72fd11c85535054ea4ffef80fa0fb8a2cd7c5d0e7de717. Exact file evidence · Machine-readable source facts · Run evidence and any recorded receipts. A checksum fingerprints only the named file bytes; it does not prove safety, quality, a complete multi-file selection or a successful run.

Updated · Page-copy source revision 8871bab84e1cf80aea1686a944ec335078a6c036 · Source files: apps/web/lib/model-page-template.mjs, apps/web/lib/model-page-v3.mjs, apps/web/lib/aeo-page.mjs · Full revision record

Model metadata: As of at the model source. Popularity counters are source-reported, not measured by Hugging Bay. Availability checked .

Key facts

Catalog record
Summarizes upstream metadata; it is not itself a download or run receipt.
File evidence
Lists exact filenames, availability and any recorded SHA-256 for individual files.
Run evidence
Reports measured results only when a receipt exists for named file bytes and a setup; otherwise unmeasured.
Checksum scope
SHA-256 fingerprints one file’s bytes; it does not prove safety, quality or a multi-file bundle.

Evidence you can inspect (plain text)

  • This page’s quick answer names the file record for hf-model-maxjeblick-llama2-0b-unit-test.
  • Open /artifact/hf-model-maxjeblick-llama2-0b-unit-test/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-maxjeblick-llama2-0b-unit-test for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-maxjeblick-llama2-0b-unit-test/card.md for machine-readable source facts (not a runtime test).
  • A matching checksum on this page fingerprints only the named bytes shown in file evidence.

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

Which date applies to which fact

  • File availability check:
  • 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.

Requirements and source record

Try browser chat with a small demo model (a separate model; device support is checked before loading).

MaxJeblick/llama2-0b-unit-test

Content controls: not assessed.

The catalog lists this model for generating text. Catalog sources: task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileSizeSHA-256SourceDownload
Weights
model.safetensors3.09 MB
5108f9b6…0e7de7175108f9b61c4c32b2ae72fd11c85535054ea4ffef80fa0fb8a2cd7c5d0e7de717
Download availability is being checked.File metadata
pytorch_model.bin3.09 MB
aecfb7cb…9dabea73aecfb7cbc2b49aeddaf9ccc404d5bc7a8a6d3ce9bad18d9f8d2d22eb9dabea73
Download availability is being checked.File metadata
Tokenizer & config
added_tokens.json42 bytes
d606246b…589a6b4cd606246b713e31b1b43dfe913554dd47819089b9e44b9ebaa294eda2589a6b4c
Download availability is being checked.File metadata
config.json684 bytes
4beb8934…5317af3c4beb89349894ef858fd148e5fdb838615ca104a4e9f2abc689b790165317af3c
Download availability is being checked.File metadata
generation_config.json111 bytes
8d7242f5…64d7fc808d7242f52ed9f3d40ab624ab7288d1db274f25255bd29571caa4862664d7fc80
Download availability is being checked.File metadata
special_tokens_map.json414 bytes
6fa06efa…34f5cfd06fa06efa2785e450051989a6f8fb4416b10149ded485ddd3f127a40734f5cfd0
Download availability is being checked.File metadata
tokenizer.json1.84 MB
bcd04f0e…43640f2ebcd04f0eadf90287bd26e1a183ac487d8a141b09b06aecb7725bbdd343640f2e
Download availability is being checked.File metadata
tokenizer.model499.7 KB
9e556afd…1818d3479e556afd44213b6bd1be2b850ebbbd98f5481437a8021afaf58ee7fb1818d347
Download availability is being checked.File metadata
tokenizer_config.json918 bytes
e3dd4025…615e0695e3dd4025f0dc9f23a8bea840afceb093dc4c3f250f6555ec0c536cc0615e0695
Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB—Download availability is being checked.File metadata
README.md2.13 KB—Download availability is being checked.File metadata

Check a download

In the folder where you saved added_tokens.json, run:

macOS
shasum -a 256 -- 'added_tokens.json'
Linux
sha256sum -- 'added_tokens.json'
Windows
Get-FileHash -LiteralPath 'added_tokens.json' -Algorithm SHA256

Compare the result with the recorded SHA-256.