unsloth/gemma-3-270m-it-torchao-FP8 warn
Weights only ship in a format that can run code when loaded; the chat template differs from its base model, which changes behavior; the weight files reference unusual code — review before loading.
claims base: google/gemma-3-270m-it · chat template: present · view on Hugging Face ↗
Scan coverageStatic battery2026-08-26Weights battery2026-08-26Behavioral batterynot rundetails
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-26 |
| Weights battery | Weights forensics: no GPU, no download | complete 2026-08-26262,144-token embedding scanned · 0 undertrained · lineage consistent · pickle audit: 5 non-standard global(s) |
| Behavioral battery | Live-inference differentials | not 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 (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 Chat template differs from claimed parent
The chat template does not match google/gemma-3-270m-it'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.994). The glitch-token data-corruption class has no candidate surface in this model.
medium Pickle references non-standard globals
The pickle imports globals outside the standard torch/numpy/collections set: torchao.quantization.Float8Tensor, torchao.float8.inference.Float8MMConfig, torchao.quantization.quantize_.workflows.float8.float8_tensor.QuantizeTensorToFloat8Kwargs, torchao.quantization.granularity.PerRow, torchao.quantization.quantize_.common.kernel_preference.KernelPreference. Common in full-model (non-state-dict) saves — each is code that runs at load time. Review before loading, or demand a safetensors release.
info Weights consistent with claimed parent google/gemma-3-270m-it
Mean cosine similarity of 64 sampled token-embedding rows against google/gemma-3-270m-it is 1.000 — the weights plausibly descend from the declared base (relation: unspecified).
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 unsloth/gemma-3-270m-it-torchao-FP8
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.
| architecture | gemma3_text · 18 layers · 640-dim |
| vocabulary | 262,144 tokens |
| license | gemma |
| serialization | no safetensors pickle |
| chat template | present (chat_template.jinja) · sha256:af95fbef33b76a50 |
| claimed lineage | google/gemma-3-270m-it |
| lineage verified | consistent vs google/gemma-3-270m-it — embedding-row cosine 1.000 |
| glitch-token surface | clean no undertrained tokens |
Full measured fingerprint
| architectures | Gemma3ForCausalLM |
| library | transformers |
| pipeline | text-generation |
| repo files | 11 — pickle: pytorch_model.bin |
| revision | 7f2647b24a1c |
| HF snapshot | 42 downloads · 0 likes · updated 2025-08-14 · captured 2026-08-25 |
| pickle audit | pytorch_model.bin — 12 standard global(s), suspicious torchao.quantization.Float8Tensor, torchao.float8.inference.Float8MMConfig, torchao.quantization.quantize_.workflows.float8.float8_tensor.QuantizeTensorToFloat8Kwargs, torchao.quantization.granularity.PerRow, torchao.quantization.quantize_.common.kernel_preference.KernelPreference |
| embedding tensor | model.embed_tokens.weight · BF16 · 262,144×640 |
| embedding norms | median 0.9945 · mean 0.9955 |
| lineage check | consistent — cosine 1 over 64 sampled rows vs google/gemma-3-270m-it |
Battery runs (1)the run trace behind the findings — what each job measured
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | complete | 2026-08-25 22:03 | 40s | 1 |
weights run 2026-08-25 — measurements
| probes run | glitch-norm-scan, zero-template-token-scan, pickle-static-analysis, lineage-norm-correlation |
| embedding tensor | model.embed_tokens.weight · BF16 · 262,144×640 |
| glitch surface | 0 undertrained, 0 plain-ASCII |
| lineage check | consistent — cosine 1 over 64 rows vs google/gemma-3-270m-it |
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/unsloth/gemma-3-270m-it-torchao-FP8)