google/gemma-3-1b-it pass
No major issues. Minor: the weights diverge from the claimed base model.
claims base: google/gemma-3-1b-pt · chat template: present · view on Hugging Face ↗
Scan coverageStatic battery2026-08-21Weights battery2026-08-20Behavioral batterynot rundetails
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-21 |
| Weights battery | Weights forensics: no GPU, no download | complete 2026-08-20262,144-token embedding scanned · 0 undertrained · lineage inconsistent |
| Behavioral battery | Live-inference differentials | not run |
Ingot runs three batteries against a model. What each one checks →
Findings
Scanned 2026-08-21 · published from a community scan.
info Gated repository
Access requires accepting the owner's terms; check the gate conditions for redistribution and field-of-use limits.
How to fix
Read the gate terms before building on the model.
- Check the gate conditions on the Hugging Face repo for redistribution and field-of-use limits — they bind your deployment, not just your download.
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.947). The glitch-token data-corruption class has no candidate surface in this model.
low Weights diverge from claimed parent google/gemma-3-1b-pt
This model declares google/gemma-3-1b-pt as its base (relation: unspecified), but mean cosine similarity of 64 sampled token-embedding rows against that parent is only 0.273 (true finetunes, merges, and quantizations sit above 0.8; independently trained weights sit near 0). Either the lineage label is wrong, or the model was so heavily re-trained, pruned, or distilled that the parent's properties (safety posture, evaluated behavior, licensing basis) should not be assumed to carry over. Verify provenance before relying on the parent's reputation.
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.
info Glitch-token echo probe: no candidate surface
Embedding-norm scan found no undertrained ASCII tokens (threshold 0.284 vs vocab median 0.9467), so the glitch-token data-corruption class has nothing to trigger on. Echo probe not applicable.
Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the model.
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.
Fingerprint
The durable profile of this model: measured weights-and-metadata facts, rebuilt on every scan and battery run. Updated 2026-08-20.
| architecture | gemma3_text |
| parameters | 999.9M |
| vocabulary | 262,144 tokens |
| license | gemma |
| serialization | safetensors |
| chat template | none |
| claimed lineage | google/gemma-3-1b-pt |
| lineage verified | inconsistent vs google/gemma-3-1b-pt — embedding-row cosine 0.273 |
| glitch-token surface | clean no undertrained tokens |
Full measured fingerprint
| architectures | Gemma3ForCausalLM |
| library | transformers |
| pipeline | text-generation |
| repo files | 10 |
| gated | manual |
| revision | dcc83ea841ab |
| HF snapshot | 5.1M downloads · 1.1k likes · updated 2025-04-04 · captured 2026-08-20 |
| embedding tensor | model.embed_tokens.weight · BF16 · 262,144×1152 |
| embedding norms | median 0.9467 · mean 0.9475 |
| lineage check | inconsistent — cosine 0.2728 over 64 sampled rows vs google/gemma-3-1b-pt |
Battery runs (2)the run trace behind the findings — what each job measured
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| gpu | complete | 2026-08-21 08:06 | 41s | 1 |
| weights | complete | 2026-08-20 18:02 | 44s | 1 |
gpu run 2026-08-21 — measurements
| probes run | glitch |
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/google/gemma-3-1b-it)