hmellor

tiny random LlamaForCausalLM

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 6 of 8 filessafetensors
Quick answer: compatibility and sources

Can I run tiny-random-LlamaForCausalLM 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.

tiny-random-LlamaForCausalLM 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: 542b957bac6c891710a57fbf82a490e6e03e19218311634d340d13f282d66b10. 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-hmellor-tiny-random-llamaforcausallm.
  • Open /artifact/hf-model-hmellor-tiny-random-llamaforcausallm/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-hmellor-tiny-random-llamaforcausallm for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-hmellor-tiny-random-llamaforcausallm/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).

hmellor/tiny-random-LlamaForCausalLM

Content controls: not assessed.

The catalog lists this model for having conversations. Catalog sources: tags, task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileTamañoSHA-256OrigenDescargar
Weights
model.safetensors2.13 MB
542b957b…82d66b10542b957bac6c891710a57fbf82a490e6e03e19218311634d340d13f282d66b10
Download availability is being checked.File metadata
Tokenizer & config
config.json691 bytes
dcbec8a5…1ac8433bdcbec8a5f89bf62e32cadc8d0cf20cddc61d41b25f2e0cf1b7e768eb1ac8433b
Download availability is being checked.File metadata
generation_config.json39 bytes
aeddd2c3…c971a7dbaeddd2c395a24f49210f116ba6f6e0b90ab44b37e37d153d74a05a8dc971a7db
Download availability is being checked.File metadata
special_tokens_map.json552 bytes
4859e5db…b2166e7f4859e5dbde90e059988a0a2136d8df3f2773d4d2fc4c4543690028f0b2166e7f
Download availability is being checked.File metadata
tokenizer.json3.62 MB
d606f46a…50e25029d606f46a8aa6f29f0a0abdec7c3ffddefc9f9bfe26919532d209a0a850e25029
Download availability is being checked.File metadata
tokenizer_config.json1.99 KB
040872e9…9d966595040872e9d5a8ba8676627762439adb9f7bc0a2b91175a679141f50009d966595
Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB—Download availability is being checked.File metadata
README.md5.17 KB—Download availability is being checked.File metadata

Comprobar una descarga

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

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

Compare the result with the recorded SHA-256.