Model page

zkolter/Llama-3.2-1B-Instruct-Simplified warn

Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo; the chat template was dropped from its base model, which changes behavior.

downloads 14likes 0license llama3.2updated 2026-03-09

claims base: meta-llama/Llama-3.2-1B-Instruct · chat template: not found · view on Hugging Face ↗

Scan coverageStatic battery2026-08-26Weights battery2026-08-26Behavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-26
Weights batteryWeights forensics: no GPU, no downloadcomplete 2026-08-26128,256-token embedding scanned · 0 undertrained · lineage consistent · pickle audit clean
Behavioral batteryLive-inference differentialsnot run

Ingot runs three batteries against a model. What each one checks →

Findings

Scanned 2026-08-26 · published from a community scan.

medium Pickle-serialized weights, no safetensors

Weights ship only as pickle-based files (consolidated.00.pth). Loading pickle executes arbitrary code from the file — prefer a safetensors release or load in a sandbox.

How to fix

Convert the weights to safetensors before loading them anywhere that matters.

  1. Do not load the pickle files in-process — pickle deserialization executes arbitrary code from the file.
  2. Convert locally in a sandbox: `pip install safetensors` and use `safetensors.torch.save_file` on a state dict loaded with `torch.load(..., weights_only=True)` (refuses most code-execution payloads), or use Hugging Face's `convert.py` space/script.
  3. Pin the exact revision hash you converted from, and load only your converted safetensors artifact from then on.

medium Repo ships executable Python (trust_remote_code)

The repository contains custom code files that run in-process when loaded with trust_remote_code=True. Pin the revision hash and review the code before loading.

How to fix

Review and pin the custom code; never float on `main` with trust_remote_code=True.

  1. Read every `.py` file in the repo before first load — this code runs in your process.
  2. Pin the revision: `from_pretrained(model_id, revision="<commit sha>", trust_remote_code=True)` so a later push can't swap the code under you.
  3. Prefer a version of the architecture already in `transformers` if one exists, which removes the remote-code requirement entirely.

medium Chat template dropped vs parent

meta-llama/Llama-3.2-1B-Instruct ships a chat template; this repo does not. Serving stacks will silently fall back to a generic template, changing behavior. (In our 296-model census, 78% of pure quantization re-releases changed or dropped the template.)

How to fixingot patch

Restore the parent's chat template in `tokenizer_config.json` — a pure metadata fix.

  1. Run `ingot patch <owner/model>` — the patch manifest carries the parent's template and applies it to a local copy's `tokenizer_config.json`.
  2. Or fix by hand: copy the `chat_template` value from the parent repo's `tokenizer_config.json` into this model's, and pin your serving stack to that file.
  3. If the drift was intentional (the author retrained on a new template), confirm that in the model card before "fixing" it — restoring the parent template on retrained weights changes behavior too.

info Embedding-norm glitch scan clean

No undertrained tokens found: every non-special token's embedding norm is above 0.3× the vocabulary median (0.952). The glitch-token data-corruption class has no candidate surface in this model.

info Pickle static analysis clean

Opcode-level parse of consolidated.00.pth (no code executed) found only standard serialization globals (3 distinct, all torch/collections/numpy). Pickle remains an executable format — this verifies the current bytes, not future uploads; prefer a safetensors release.

info Weights consistent with claimed parent meta-llama/Llama-3.2-1B-Instruct

Mean cosine similarity of 64 sampled token-embedding rows against meta-llama/Llama-3.2-1B-Instruct is 0.960 — the weights plausibly descend from the declared base (relation: unspecified).

Put this result in your workflow

Check every checkpoint before it ships

Use the web app, API, CLI, or CI gate to scan candidate checkpoints and catch model drift before deployment. Public-model scans publish to the open database; paid plans add the volume needed for continuous checks.

Fix it

Some findings are metadata-level and patchable — apply the fixes to your local copy (your weights never leave your machine):

npx @ingotai/scan patch zkolter/Llama-3.2-1B-Instruct-Simplified

Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the model.

Fingerprint

The durable profile of this model: measured weights-and-metadata facts, rebuilt on every scan and battery run. Updated 2026-08-26.

vocabulary128,256 tokens
licensellama3.2
serializationno safetensors pickle custom code
chat templatenone
claimed lineagemeta-llama/Llama-3.2-1B-Instruct
lineage verifiedconsistent vs meta-llama/Llama-3.2-1B-Instruct — embedding-row cosine 0.960
glitch-token surfaceclean no undertrained tokens
Full measured fingerprint
pipelinetext-generation
repo files6 — pickle: consolidated.00.pth
revisionfea2dfb0494b
HF snapshot15 downloads · 0 likes · updated 2026-03-09 · captured 2026-08-25
pickle auditconsolidated.00.pth — 3 standard global(s)
embedding tensortok_embeddings.weight · BF16 · 128,256×2048
embedding normsmedian 0.9516 · mean 0.9485
lineage checkconsistent — cosine 0.9596 over 64 sampled rows vs meta-llama/Llama-3.2-1B-Instruct
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-25 22:2847s1
weights run 2026-08-25 — measurements
probes runglitch-norm-scan, zero-template-token-scan, pickle-static-analysis, lineage-norm-correlation
probes skippedtoken-decode: no tokenizer.json
embedding tensortok_embeddings.weight · BF16 · 128,256×2048
glitch surface0 undertrained, 0 plain-ASCII
lineage checkconsistent — cosine 0.9596 over 64 rows vs meta-llama/Llama-3.2-1B-Instruct

Verdict badge

Ship the verdict in your README — it always shows the latest published analysis:

Ingot verdict: warn

[![Ingot scan](https://ingot.tools/api/v1/models/zkolter/Llama-3.2-1B-Instruct-Simplified/badge.svg)](https://ingot.tools/models/zkolter/Llama-3.2-1B-Instruct-Simplified)
Gate it in CI