Model page

Qwen/Qwen2.5-3B-Instruct warn

The chat template differs from its base model, which changes behavior.

downloads 4.2Mlikes 587license otherarch qwen2params 3085.9Mupdated 2024-09-25

claims base: Qwen/Qwen2.5-3B · chat template: present · view on Hugging Face ↗

Scan coverageStatic battery2026-08-21Weights battery2026-08-20Behavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics: no GPU, no downloadcomplete 2026-08-20151,936-token embedding scanned · 0 undertrained · lineage consistent
Behavioral batteryLive-inference differentialsnot run

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

Findings

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

medium Chat template differs from claimed parent

The chat template does not match Qwen/Qwen2.5-3B'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.

  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 (1.113). The glitch-token data-corruption class has no candidate surface in this model.

info Weights consistent with claimed parent Qwen/Qwen2.5-3B

Mean cosine similarity of 64 sampled token-embedding rows against Qwen/Qwen2.5-3B is 1.000 — the weights plausibly descend from the declared base (relation: unspecified).

info Glitch-token echo probe: no candidate surface

Embedding-norm scan found no undertrained ASCII tokens (threshold 0.3339 vs vocab median 1.1131), so the glitch-token data-corruption class has nothing to trigger on. Echo probe not applicable.

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 Qwen/Qwen2.5-3B-Instruct

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-20.

architectureqwen2 · 36 layers · 2048-dim
parameters3085.9M
vocabulary151,936 tokens
licenseother
serializationsafetensors
chat templatepresent · sha256:cd8e9439f0570856
claimed lineageQwen/Qwen2.5-3B
lineage verifiedconsistent vs Qwen/Qwen2.5-3B — embedding-row cosine 1.000
glitch-token surfaceclean no undertrained tokens
Full measured fingerprint
architecturesQwen2ForCausalLM
librarytransformers
pipelinetext-generation
repo files12
revisionaa8e72537993
HF snapshot7.0M downloads · 552 likes · updated 2024-09-25 · captured 2026-08-20
embedding tensormodel.embed_tokens.weight · BF16 · 151,936×2048
embedding normsmedian 1.1131 · mean 1.089
lineage checkconsistent — cosine 0.9996 over 64 sampled rows vs Qwen/Qwen2.5-3B
Battery runs (4)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
gpucomplete2026-08-21 08:0637s1
weightscomplete2026-08-20 18:0239s1
weightscomplete2026-08-20 08:1039s1
weightscomplete2026-08-20 06:3451s1
gpu run 2026-08-21 — measurements
probes runglitch

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/Qwen/Qwen2.5-3B-Instruct/badge.svg)](https://ingot.tools/models/Qwen/Qwen2.5-3B-Instruct)
Gate it in CI