nicoboss

Llama 3.2 1B Uncensored

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
generalLicense: llama3.2SHA-256 recorded for 6 of 8 filessafetensors
Quick answer: compatibility and sources

Can I run Llama-3.2-1B-Instruct-Uncensored 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.

Llama-3.2-1B-Instruct-Uncensored is an open-weights language model for general. 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: cc7f465e8f89cf99d07b4c575ebca1fec05e14d4c4954108a9d520356014c18c. 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-nicoboss-llama-3-2-1b-instruct-uncensored.
  • Open /artifact/hf-model-nicoboss-llama-3-2-1b-instruct-uncensored/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-nicoboss-llama-3-2-1b-instruct-uncensored for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-nicoboss-llama-3-2-1b-instruct-uncensored/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
nicoboss/Llama-3.2-1B-Instruct-Uncensored

Content controls: not assessed.

The catalog does not give enough information to describe what this model is for. Catalog sources: license, cardMetadata.license, baseModel, cardMetadata.libraryName.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileTailleSHA-256SourceTélécharger
Weights
model.safetensors2.47 GB
cc7f465e…6014c18ccc7f465e8f89cf99d07b4c575ebca1fec05e14d4c4954108a9d520356014c18c
Download availability is being checked.File metadata
Tokenizer & config
config.json889 bytes
df41cd26…1b55199bdf41cd264f23fe0042281cea0246b5b48ff56173849fb2b84b2ab0b91b55199b
Download availability is being checked.File metadata
generation_config.json184 bytes
f571455b…4e038f71f571455b7715ad274df4ffe832ab20e374e2ea1d6fde467a80e04da04e038f71
Download availability is being checked.File metadata
special_tokens_map.json444 bytes
7a6d7fa8…2f8078077a6d7fa83a01e8192333cd7b848541159709c4b206739071980432612f807807
Download availability is being checked.File metadata
tokenizer.json17.2 MB
6b9e4e7f…be39537b6b9e4e7fb171f92fd137b777cc2714bf87d11576700a1dcd7a399e7bbe39537b
Download availability is being checked.File metadata
tokenizer_config.json51 KB
670813e0…7e58287b670813e0531d7ca52d63436825ea2c26288e1067a0f7c7689ae9599b7e58287b
Download availability is being checked.File metadata
Docs
.gitattributes1.57 KB—Download availability is being checked.File metadata
README.md5.51 KB—Download availability is being checked.File metadata

Vérifier un téléchargement

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.