Model page

unsloth/Qwen3-Coder-30B-A3B-Instruct-GGUF warn

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

downloads 7.8Mlikes 1.1klicense apache-2.0updated 2026-01-30

claims base: Qwen/Qwen3-Coder-30B-A3B-Instruct · chat template: not found · view on Hugging Face ↗

Scan coverageStatic battery2026-08-20Weights batteryfailedBehavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-20
Weights batteryWeights forensics: no GPU, no downloadfailed429 Too Many Requests for https://huggingface.co/api/models/unsloth/Qwen3-Coder-30B-A3B-Instruct-GGUF
Behavioral batteryLive-inference differentialsnot run

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

Findings

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

medium Chat template dropped vs parent

Qwen/Qwen3-Coder-30B-A3B-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.

  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.
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 unsloth/Qwen3-Coder-30B-A3B-Instruct-GGUF

Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the model.

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/unsloth/Qwen3-Coder-30B-A3B-Instruct-GGUF/badge.svg)](https://ingot.tools/models/unsloth/Qwen3-Coder-30B-A3B-Instruct-GGUF)
Gate it in CI