MaziyarPanahi/Qwen2.5-7B-Instruct-GGUF warn
No license declared — no usage rights by default; the chat template was dropped from its base model, which changes behavior; its architecture doesn't match its claimed base model.
claims base: Qwen/Qwen2.5-7B-Instruct · chat template: not found · view on Hugging Face ↗
Scan coverageStatic battery2026-08-21Weights batteryfailedBehavioral batterynot rundetails
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-21 |
| Weights battery | Weights forensics: no GPU, no download | failed429 Too Many Requests for https://huggingface.co/api/models/MaziyarPanahi/Qwen2.5-7B-Instruct-GGUF |
| 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 No license declared
The model card declares no license. You have no usage rights by default — treat as all-rights-reserved until the owner clarifies.
How to fix
Get a license from the owner or pick a licensed alternative — this is a legal gap, not a technical one.
- With no declared license you have no usage rights by default; treat the weights as all-rights-reserved.
- Open an issue or discussion on the repo asking the owner to declare a license, or use the licensed upstream/parent model instead.
medium Chat template dropped vs parent
Qwen/Qwen2.5-7B-Instruct ships a chat template; this repo does not. Serving stacks will silently fall back to a generic template, changing behavior. (In our 296-model census, 78% of pure quantization re-releases changed or dropped the template.)
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 Architecture differs from claimed parent (mistral vs qwen2)
This model declares Qwen/Qwen2.5-7B-Instruct as its base, but its config declares architecture 'mistral' while the parent is 'qwen2'. A finetune, merge, or quantization cannot change the architecture family — the lineage label is wrong or misleading, so treat provenance claims (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 MaziyarPanahi/Qwen2.5-7B-Instruct-GGUF
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 | mistral |
| license | none declared |
| serialization | gguf |
| chat template | none |
| claimed lineage | Qwen/Qwen2.5-7B-Instruct |
| lineage verified | unverified — weights battery pending |
Full measured fingerprint
| pipeline | text-generation |
| repo files | 20 |
| revision | 113085215169 |
| HF snapshot | 180.9k downloads · 11 likes · updated 2024-09-18 · captured 2026-08-21 |
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/MaziyarPanahi/Qwen2.5-7B-Instruct-GGUF)