Eeppa

TinyBuddy-80K

Code
What we checked

File: check availability in Files.

Memory: Fit unknown. File size needed to check fit.

Last recorded run: none for this selected file.

License BFiles CRuns F

Recorded checks do not guarantee safety or performance on your computer.

See file checks and sources
Model details
Chat & writeLicense label: mitNeeds its own code to runSHA-256 recorded for 6 of 10 filessafetensors
Quick answer: compatibility and sources

Can I run TinyBuddy-80K 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.

TinyBuddy-80K 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: e008fdfb257851669f1316cfe95d315e0619d0569a499cb84fccad2222a304e0. 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.

Page text updated .

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-eeppa-tinybuddy-80k.
  • Open /artifact/hf-model-eeppa-tinybuddy-80k/files for exact filenames, availability and any recorded SHA-256 for this model.
  • Open /evidence/artifacts/hf-model-eeppa-tinybuddy-80k for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-eeppa-tinybuddy-80k/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).

Eeppa/TinyBuddy-80K

Content controls: not assessed.

The catalog lists this model for generating text. Catalog sources: license label, model card license, task label, model card task.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileTamañoSHA-256OrigenDescargar
Weights
model.safetensors555.9 KB
e008fdfb…22a304e0e008fdfb257851669f1316cfe95d315e0619d0569a499cb84fccad2222a304e0
Download availability is being checked.File metadata
Tokenizer & config
config.json871 bytes
e7ccb783…b32d3e7be7ccb7833eaa69ac5b241869676c15ef34eeb5dcb3bad410170bf0edb32d3e7b
Download availability is being checked.File metadata
configuration_tinybuddy.py1.31 KB-Download availability is being checked.File metadata
modeling_tinybuddy.py6.53 KB-Download availability is being checked.File metadata
special_tokens_map.json98 bytes
37475779…4973e020374757794ca394ad14bb051fb3415873ae5c92660ac89383f666b7094973e020
Download availability is being checked.File metadata
tokenizer.json63.6 KB
28f6bce5…f9ea984a28f6bce554e927444629b5e14cf634470f0b098316ee1d98e3268665f9ea984a
Download availability is being checked.File metadata
tokenizer_config.json264 bytes
eaa8567e…ad4a2e41eaa8567ee36243224d8fc9ab0108719dc354948ae9395688356ab07fad4a2e41
Download availability is being checked.File metadata
__init__.py0 bytes-Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB-Download availability is being checked.File metadata
README.md3.95 KB
90f99e1a…3e6240b690f99e1aef91d3412eafc810f22874bd14de6742bbc678c8a286ced03e6240b6
Download availability is being checked.File metadata

Comprobar una descarga

In the folder where you saved README.md, run:

macOS
shasum -a 256 -- 'README.md'
Linux
sha256sum -- 'README.md'
Windows
Get-FileHash -LiteralPath 'README.md' -Algorithm SHA256

Compare the result with the recorded SHA-256.