nguyenthanhthuan/Llama_3.2_1B_Intruct_Tool_Calling_V2 warn
Weights only ship in a format that can run code when loaded; its license differs from its base model's; the chat template differs from its base model, which changes behavior. Plus 1 minor note.
claims base: meta-llama/Llama-3.2-1B-Instruct · chat template: present · view on Hugging Face ↗
Scan coverageStatic battery2026-08-25Weights battery2026-08-25Behavioral batterynot rundetails
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-25 |
| Weights battery | Weights forensics — no GPU, no download | complete 2026-08-25128,256-token embedding scanned · 0 undertrained · lineage consistent · pickle audit clean |
| Behavioral battery | Live-inference differentials | not run |
Ingot runs three batteries against a model. What each one checks →
Findings
Scanned 2026-08-25 · published from a community scan.
medium Pickle-serialized weights, no safetensors
Weights ship only as pickle-based files (pytorch_model.bin). 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.
- Do not load the pickle files in-process — pickle deserialization executes arbitrary code from the file.
- 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.
- Pin the exact revision hash you converted from, and load only your converted safetensors artifact from then on.
medium License differs from claimed parent (apache-2.0 vs llama3.2)
This model declares apache-2.0 while its claimed base meta-llama/Llama-3.2-1B-Instruct declares llama3.2. Verify the re-license is permitted before commercial use.
How to fix
Verify the re-license is actually permitted before relying on it.
- Read the parent's license for derivative-work and re-licensing terms — many open-weight licenses (e.g. Llama-family) do not permit arbitrary re-licensing.
- If the re-license is not permitted, the parent's terms govern your use regardless of what this repo declares.
medium Chat template differs from claimed parent
The chat template does not match meta-llama/Llama-3.2-1B-Instruct's. Template drift silently changes model behavior even when weights are identical — 37% of drifted derivatives in our census left it undisclosed. Diff the templates before deploying.
How to fixingot patch
Restore the parent's chat template in `tokenizer_config.json` — a pure metadata fix.
- Run `ingot patch <owner/model>` — the patch manifest carries the parent's template and applies it to a local copy's `tokenizer_config.json`.
- 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.
- 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.933). The glitch-token data-corruption class has no candidate surface in this model.
info Pickle static analysis clean
Opcode-level parse of pytorch_model.bin (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 1.000 — the weights plausibly descend from the declared base (relation: unspecified).
How to fix
Fix or verify the `base_model` declaration so lineage checks can run.
- If you own the repo: correct the `base_model` field in the model card metadata to the real, public parent.
- If you don't: identify the true parent (config architecture + weight shapes narrow it fast) and re-scan with that lineage in mind.
low GGUF chat template differs from the source repo's
The template embedded at conversion time (848 chars) no longer matches the source repo's current template (3827 chars). Source-repo template fixes never propagate into converted GGUFs — 43% of popular GGUF repos drift this way, including quants that resurrect already-fixed launch bugs. Diff the two before deploying; re-embed with gguf-py if the source's fix matters.
How to fixingot patch
Fix the GGUF's embedded metadata in place with gguf-py — template, EOS id, and pre-tokenizer are all metadata-editable; no requant needed.
- Template or EOS drift: copy the current values from the source repo and write them into the GGUF (`gguf_set_metadata.py` / gguf-py) — the tensor data is untouched.
- Missing pre-tokenizer type: reconvert with a current `convert_hf_to_gguf.py`, or set the correct `tokenizer.ggml.pre` for the architecture.
- Until the file is fixed, override at load time: llama.cpp `--override-kv tokenizer.ggml.eos_token_id=int:<id>` and `--chat-template-file <fixed.jinja>`.
- Prefer a re-upload from the quantizer once the source repo's fix lands — already-downloaded GGUFs never pick up upstream fixes on their own.
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 nguyenthanhthuan/Llama_3.2_1B_Intruct_Tool_Calling_V2
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-25.
| architecture | llama · 16 layers · 2048-dim |
| vocabulary | 128,256 tokens |
| license | apache-2.0 |
| serialization | gguf pickle |
| chat template | present · sha256:275c67ccdd993de1 |
| claimed lineage | meta-llama/Llama-3.2-1B-Instruct |
| lineage verified | consistent vs meta-llama/Llama-3.2-1B-Instruct — embedding-row cosine 1.000 |
| glitch-token surface | clean no undertrained tokens |
Full measured fingerprint
| architectures | LlamaForCausalLM |
| library | transformers |
| pipeline | text-generation |
| repo files | 10 — pickle: pytorch_model.bin |
| revision | ea7d42055f52 |
| HF snapshot | 503 downloads · 8 likes · updated 2024-10-28 · captured 2026-08-25 |
| pickle audit | pytorch_model.bin — 3 standard global(s) |
| embedding tensor | model.embed_tokens.weight · F16 · 128,256×2048 |
| embedding norms | median 0.9333 · mean 0.9298 |
| lineage check | consistent — cosine 1 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
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | complete | 2026-08-25 21:48 | 72s | 1 |
weights run 2026-08-25 — measurements
| probes run | glitch-norm-scan, zero-template-token-scan, pickle-static-analysis, lineage-norm-correlation, gguf-metadata |
| embedding tensor | model.embed_tokens.weight · F16 · 128,256×2048 |
| glitch surface | 0 undertrained, 0 plain-ASCII |
| lineage check | consistent — cosine 1 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:
[](https://ingot.tools/models/nguyenthanhthuan/Llama_3.2_1B_Intruct_Tool_Calling_V2)