l3lab/L1-Qwen3-8B-Exact warn
Its license differs from its base model's; the chat template differs from its base model, which changes behavior; its tokenizer differs from its claimed base model. Plus 2 more issues.
claims base: deepseek-ai/DeepSeek-R1-Distill-Qwen-7B · chat template: present · view on Hugging Face ↗
Scan coverageStatic battery2026-08-21Weights battery2026-08-21Behavioral 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-21151,936-token embedding scanned · 2999 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.
medium License differs from claimed parent (apache-2.0 vs mit)
This model declares apache-2.0 while its claimed base deepseek-ai/DeepSeek-R1-Distill-Qwen-7B declares mit. 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 deepseek-ai/DeepSeek-R1-Distill-Qwen-7B'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.
medium Vocabulary size differs from claimed parent (151936 vs 152064)
A changed vocab means changed tokenization: strings will split differently than on deepseek-ai/DeepSeek-R1-Distill-Qwen-7B, which can shift behavior on identifiers, codes, and non-English text.
How to fixweight-level
Not patchable: the vocab size mirrors the embedding matrix in the weights. Verify the change was intentional.
- Do not edit `vocab_size` in config.json to "match the parent" — it must equal the embedding table in the shipped weights or the model won't load.
- Diff the tokenizers (`tokenizer.json` / added_tokens) against the parent to see what was added or removed, and test your own identifiers, codes, and non-English text through both.
- If the drift is unexplained by the model card, treat tokenization-sensitive behavior as unvalidated on this model.
medium Undertrained (glitch) token surface in vocabulary
Embedding-norm scan flagged 2999 undertrained tokens (norm < 0.3× the vocabulary median of 1.451), including 102 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "$PostalCodesNL", "ForCanBeConvertedToF", "PostalCodesNL", "ForCanBeConverted", "useRalative", "thuisontvangst", "useRal", "sexkontakte". In models where this class was tested behaviorally, such tokens silently rewrote user input into confident, schema-valid, wrong output. These are candidates from the weights alone; behavioral confirmation requires the behavioral battery.
How to fixruntime guardweight-level
Keep the affected token strings out of the model's input — the scan-derived runtime guard carries this model's exact blocklist.
- Fetch this model's guard artifact (`/api/v1/guard/<owner>/<model>`): the confirmed corrupting tokens and the low-norm candidate list, derived from the published scan.
- Screen inbound text with it (the `@ingotai/guard` package is a reference implementation) and route flagged records to a different model or human review — verbatim-copy tasks on flagged strings are the failure mode.
- The underlying cause is undertrained embeddings in the weights; a true fix is weight-level (continued pretraining on the affected tokens) — that is not a patch, it's a training job.
medium Weights inconsistent with claimed parent deepseek-ai/DeepSeek-R1-Distill-Qwen-7B
This model declares deepseek-ai/DeepSeek-R1-Distill-Qwen-7B as its base (relation: unspecified), but its token-embedding geometry is incompatible: 4096-dim embeddings vs the parent's 3584-dim. A finetune cannot change embedding width — the lineage label is wrong or misleading. Treat provenance claims on this repo (training data, safety posture, licensing) as unverified.
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.
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 l3lab/L1-Qwen3-8B-Exact
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-21.
| architecture | qwen3 · 36 layers · 4096-dim |
| parameters | 8190.7M |
| vocabulary | 151,936 tokens |
| license | apache-2.0 |
| serialization | safetensors |
| chat template | present · sha256:87a2728cb8dc9fe4 |
| claimed lineage | deepseek-ai/DeepSeek-R1-Distill-Qwen-7B |
| lineage verified | inconsistent vs deepseek-ai/DeepSeek-R1-Distill-Qwen-7B |
| glitch-token surface | 2,999 undertrained candidates, 102 plain-ASCII |
Full measured fingerprint
| architectures | Qwen3ForCausalLM |
| repo files | 13 |
| revision | d1ded71219d1 |
| HF snapshot | 220 downloads · 1 likes · updated 2025-07-13 · captured 2026-08-21 |
| embedding tensor | model.embed_tokens.weight · BF16 · 151,936×4096 |
| embedding norms | median 1.4512 · mean 1.3758 |
| lineage check | inconsistent — cosine undefined over undefined sampled rows vs deepseek-ai/DeepSeek-R1-Distill-Qwen-7B |
| glitch-token samples | "$PostalCodesNL", "ForCanBeConvertedToF", "PostalCodesNL", "ForCanBeConverted", "useRalative", "thuisontvangst", "useRal", "sexkontakte", "NdrFc", "webElementX", "sextreffen", "wannonce" |
Battery runs (1)the run trace behind the findings — what each job measured
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | complete | 2026-08-21 05:17 | 11m | 1 |
weights run 2026-08-21 — measurements
| probes run | glitch-norm-scan, lineage-norm-correlation |
| embedding tensor | model.embed_tokens.weight · BF16 · 151,936×4096 |
| glitch surface | 2,999 undertrained, 102 plain-ASCII |
| lineage check | inconsistent — cosine undefined over undefined rows vs deepseek-ai/DeepSeek-R1-Distill-Qwen-7B |
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/l3lab/L1-Qwen3-8B-Exact)