second-state/Phi-3-mini-4k-instruct-GGUF warn
Loading it runs custom code from the repo; the chat template was dropped from its base model, which changes behavior.
Could not load this model from the Hugging Face API (private, gated, or nonexistent). Findings below are from our archive.
Scan coverageStatic battery2026-08-21Weights batteryn/aBehavioral batterynot rundetails
| 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 |
Ingot runs three batteries against a model. What each one checks →
Findings
Scanned 2026-08-21 · published from a community scan.
medium Repo ships executable Python (trust_remote_code)
The repository contains custom code files that run in-process when loaded with trust_remote_code=True. Pin the revision hash and review the code before loading.
How to fix
Review and pin the custom code; never float on `main` with trust_remote_code=True.
- Read every `.py` file in the repo before first load — this code runs in your process.
- Pin the revision: `from_pretrained(model_id, revision="<commit sha>", trust_remote_code=True)` so a later push can't swap the code under you.
- Prefer a version of the architecture already in `transformers` if one exists, which removes the remote-code requirement entirely.
medium Chat template dropped vs parent
microsoft/Phi-3-mini-4k-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.
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 second-state/Phi-3-mini-4k-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 | phi3 · 32 layers · 3072-dim |
| vocabulary | 32,064 tokens |
| license | mit |
| serialization | gguf custom code |
| chat template | none |
| claimed lineage | microsoft/Phi-3-mini-4k-instruct |
| lineage verified | unverified — weights battery pending |
Full measured fingerprint
| architectures | Phi3ForCausalLM |
| library | transformers |
| pipeline | text-generation |
| repo files | 17 |
| revision | 33b62d809bd9 |
| HF snapshot | 2.4k downloads · 5 likes · updated 2024-07-29 · 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 (1)the run trace behind the findings — what each job measured
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | complete | 2026-08-21 05:11 | 0s | 1 |
weights run 2026-08-21 — measurements
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/second-state/Phi-3-mini-4k-instruct-GGUF)