AdnanRiaz107

SantaCoder MBPP

Question answering

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
question answeringLicense: mitSHA-256 recorded for 6 of 11 filessafetensors
Quick answer: compatibility and sources

Can I run SantaCoder-MBPP 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.

SantaCoder-MBPP is an open-weights language model for question answering. 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: 03fb58ee6c0de41d8985715401164ded1ddf113f717c7c3015e9338861b3d89d. 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-adnanriaz107-santacoder-mbpp.
  • Open /artifact/hf-model-adnanriaz107-santacoder-mbpp/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-adnanriaz107-santacoder-mbpp for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-adnanriaz107-santacoder-mbpp/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
AdnanRiaz107/SantaCoder-MBPP

Content controls: not assessed.

The catalog lists this model as an add-on for answering questions. Catalog sources: license, cardMetadata.license, files, task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileSizeSHA-256SourceDownload
Weights
model.safetensors11 MB
03fb58ee…61b3d89d03fb58ee6c0de41d8985715401164ded1ddf113f717c7c3015e9338861b3d89d
Download availability is being checked.File metadata
Tokenizer & config
adapter_config.json629 bytes—Download availability is being checked.File metadata
added_tokens.json126 bytes
9340bea5…1a7a9d6e9340bea5aa7128d4875890c81ba8b96d6667d8d45de1ef538028f68f1a7a9d6e
Download availability is being checked.File metadata
config.json1.03 KB
f9b1c229…bef3bed9f9b1c229f8cb867176f5ac674336f462ea448b19a5ba55fdbfae682dbef3bed9
Download availability is being checked.File metadata
merges.txt454.9 KB—Download availability is being checked.File metadata
special_tokens_map.json494 bytes
816fe58b…200c438f816fe58bfd13dda7a398e3cf4ebfc3d3d522359f23e68105d76b6085200c438f
Download availability is being checked.File metadata
tokenizer.json2.08 MB
4b7cb19d…526769674b7cb19d8efb3ce03f4dcf510b395c2255b39d843a341ca3a11c98c452676967
Download availability is being checked.File metadata
tokenizer_config.json1.4 KB
9f545fdb…af138de69f545fdb9856f726fd8520e93e40a63bf67938bde5f7d63dd72c0447af138de6
Download availability is being checked.File metadata
vocab.json789.9 KB—Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB—Download availability is being checked.File metadata
README.md5.26 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.