haven-ai-companion/haven-chat-v4.0 warn
claims base: google/gemma-2-9b-it · chat template: not found · view on Hugging Face ↗
Scan coverage
Ingot runs three batteries against a model. What each one checks →
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-21 |
| Weights battery | Weights forensics — no GPU, no download | n/arepo ships no scannable weights (no safetensors and no pickle checkpoints — GGUF/CoreML/other formats) |
| Behavioral battery | Live-inference differentials | not run |
Findings
Scanned 2026-08-21 · published from a community scan.
medium License differs from claimed parent (apache-2.0 vs gemma)
This model declares apache-2.0 while its claimed base google/gemma-2-9b-it declares gemma. 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 dropped vs parent
google/gemma-2-9b-it 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.
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.
| license | apache-2.0 |
| serialization | gguf |
| chat template | none |
| claimed lineage | google/gemma-2-9b-it |
| lineage verified | unverified — weights battery pending |
Full measured fingerprint
| pipeline | text-generation |
| repo files | 3 |
| revision | b59644878d49 |
| HF snapshot | 301 downloads · 0 likes · updated 2026-08-13 · captured 2026-08-21 |
| weights battery | token-embedding scan n/a — repo ships no scannable weights (no safetensors and no pickle checkpoints — GGUF/CoreML/other formats) |
Battery runs
The run trace behind the findings above: every deep-battery job for this model, with what each run measured or why it failed. Findings are only as good as the runs that produced them.
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | complete | 2026-08-21 05:15 | 0s | 1 |
weights run 2026-08-21 — measurements
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 haven-ai-companion/haven-chat-v4.0
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:
[](https://ingot.tools/models/haven-ai-companion/haven-chat-v4.0)