MahmoudMohamed/Phi3_MeetingQA warn
Weights only ship in a format that can run code when loaded; Chat template ends turns with <|end|>, which is not a configured stop token; its license differs from its base model's. Plus 2 more issues.
Could not load this model from the Hugging Face API (private, gated, or nonexistent). Findings below are from our archive.
Scan coverageStatic battery2026-08-25Weights batteryqueuedBehavioral batterynot rundetails
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-25 |
| Weights battery | Weights forensics — no GPU, no download | queued |
| Behavioral battery | Live-inference differentials | not run |
Ingot runs three batteries against a model. What each one checks →
Findings
Scanned 2026-08-25 · published from a community scan.
medium Pickle-serialized weights, no safetensors
Weights ship only as pickle-based files (pytorch_model-00001-of-00002.bin, pytorch_model-00002-of-00002.bin). Loading pickle executes arbitrary code from the file — prefer a safetensors release or load in a sandbox.
How to fix
Convert the weights to safetensors before loading them anywhere that matters.
- Do not load the pickle files in-process — pickle deserialization executes arbitrary code from the file.
- Convert locally in a sandbox: `pip install safetensors` and use `safetensors.torch.save_file` on a state dict loaded with `torch.load(..., weights_only=True)` (refuses most code-execution payloads), or use Hugging Face's `convert.py` space/script.
- Pin the exact revision hash you converted from, and load only your converted safetensors artifact from then on.
low Padding token is the EOS token
The pad token and the (only) EOS token are the same. Fine-tuning frameworks mask pad positions out of the loss, so training on this checkpoint teaches the model to never emit EOS — the Phi-4 / Qwen 2.5 / DeepSeek R1 infinite-generation bug. Safe to serve, hazardous to fine-tune; repoint pad_token at a dedicated token first.
How to fixingot patch
Align the stop-token declarations — a pure metadata fix to `generation_config.json` (and `config.json`).
- Identify the token the chat template actually ends assistant turns with (e.g. `<|eot_id|>`, `<end_of_turn>`, `<|im_end|>`) and make sure its id is in `generation_config.json`'s `eos_token_id` list.
- Keep `config.json`'s `eos_token_id` consistent with (or a subset of) `generation_config.json`'s — runtimes differ in which file they read.
- For the pad-equals-EOS hazard: repoint `pad_token` at a dedicated padding token before fine-tuning; serving is unaffected.
- Until the repo is fixed, pass explicit stop tokens to your serving stack (e.g. vLLM `stop_token_ids`, llama.cpp `--override-kv tokenizer.ggml.eos_token_id`).
medium Chat template ends turns with <|end|>, which is not a configured stop token
The chat template terminates assistant turns with <|end|>, but the effective EOS set (config.json ∪ generation_config.json = [32000] → ["<|endoftext|>"]) never stops on it. Config-honoring runtimes generate past the terminator until the token budget is exhausted — runaway cost and self-continuing fake turns. Add <|end|>'s id to generation_config.json's eos_token_id.
How to fixingot patch
Align the stop-token declarations — a pure metadata fix to `generation_config.json` (and `config.json`).
- Identify the token the chat template actually ends assistant turns with (e.g. `<|eot_id|>`, `<end_of_turn>`, `<|im_end|>`) and make sure its id is in `generation_config.json`'s `eos_token_id` list.
- Keep `config.json`'s `eos_token_id` consistent with (or a subset of) `generation_config.json`'s — runtimes differ in which file they read.
- For the pad-equals-EOS hazard: repoint `pad_token` at a dedicated padding token before fine-tuning; serving is unaffected.
- Until the repo is fixed, pass explicit stop tokens to your serving stack (e.g. vLLM `stop_token_ids`, llama.cpp `--override-kv tokenizer.ggml.eos_token_id`).
medium License differs from claimed parent (apache-2.0 vs mit)
This model declares apache-2.0 while its claimed base unsloth/Phi-3-mini-4k-instruct-bnb-4bit 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 unsloth/Phi-3-mini-4k-instruct-bnb-4bit'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 Stop token dropped vs claimed parent but still used by the template
unsloth/Phi-3-mini-4k-instruct-bnb-4bit stops on [32000,32001,32007]; this repo only stops on [32000], losing <|assistant|> (32001), <|end|> (32007) — which this repo's own chat template still emits. Config-honoring runtimes will generate straight past it. Restore the lost id(s) to generation_config.json's eos_token_id.
How to fixingot patch
Align the stop-token declarations — a pure metadata fix to `generation_config.json` (and `config.json`).
- Identify the token the chat template actually ends assistant turns with (e.g. `<|eot_id|>`, `<end_of_turn>`, `<|im_end|>`) and make sure its id is in `generation_config.json`'s `eos_token_id` list.
- Keep `config.json`'s `eos_token_id` consistent with (or a subset of) `generation_config.json`'s — runtimes differ in which file they read.
- For the pad-equals-EOS hazard: repoint `pad_token` at a dedicated padding token before fine-tuning; serving is unaffected.
- Until the repo is fixed, pass explicit stop tokens to your serving stack (e.g. vLLM `stop_token_ids`, llama.cpp `--override-kv tokenizer.ggml.eos_token_id`).
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 MahmoudMohamed/Phi3_MeetingQA
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-25.
| architecture | mistral · 32 layers · 3072-dim |
| vocabulary | 32,064 tokens |
| license | apache-2.0 |
| serialization | no safetensors pickle |
| chat template | present · sha256:41ffe9d71dd7c901 |
| claimed lineage | unsloth/Phi-3-mini-4k-instruct-bnb-4bit |
| lineage verified | unverified — weights battery pending |
Full measured fingerprint
| architectures | MistralForCausalLM |
| library | transformers |
| pipeline | text-generation |
| repo files | 12 — pickle: pytorch_model-00001-of-00002.bin, pytorch_model-00002-of-00002.bin |
| revision | ca6592491e17 |
| HF snapshot | 18 downloads · 0 likes · updated 2024-05-05 · captured 2026-08-25 |
Battery runs (1)the run trace behind the findings — what each job measured
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | queued | 2026-08-25 22:18 | — | 0 |
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/MahmoudMohamed/Phi3_MeetingQA)