Model page

OpenVINO/Phi-4-mini-instruct-int4-ov warn

Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo; the chat template differs from its base model, which changes behavior. Plus 2 minor notes.

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 battery2026-08-25Behavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-25
Weights batteryWeights forensics — no GPU, no downloadcomplete 2026-08-25no token vocabulary — pickle audit only · pickle audit clean
Behavioral batteryLive-inference differentialsnot 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 (openvino_detokenizer.bin, openvino_model.bin, openvino_tokenizer.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.

  1. Do not load the pickle files in-process — pickle deserialization executes arbitrary code from the file.
  2. 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.
  3. Pin the exact revision hash you converted from, and load only your converted safetensors artifact from then on.

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.

  1. Read every `.py` file in the repo before first load — this code runs in your process.
  2. 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.
  3. Prefer a version of the architecture already in `transformers` if one exists, which removes the remote-code requirement entirely.

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`).

  1. 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.
  2. Keep `config.json`'s `eos_token_id` consistent with (or a subset of) `generation_config.json`'s — runtimes differ in which file they read.
  3. For the pad-equals-EOS hazard: repoint `pad_token` at a dedicated padding token before fine-tuning; serving is unaffected.
  4. 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 differs from claimed parent

The chat template does not match microsoft/Phi-4-mini-instruct'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.

  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.

info Pickle static analysis clean

Opcode-level parse of openvino_detokenizer.bin, openvino_model.bin, openvino_tokenizer.bin (no code executed) found only standard serialization globals (0 distinct, all torch/collections/numpy). Pickle remains an executable format — this verifies the current bytes, not future uploads; prefer a safetensors release.

low Pickle checkpoint only partially analyzable

Static analysis could not fully parse: openvino_detokenizer.bin: legacy parse stopped after 0 pickle(s): unsupported pickle opcode 0x0 at 0, openvino_model.bin: legacy parse stopped after 0 pickle(s): unsupported pickle opcode 0x0 at 0, openvino_tokenizer.bin: legacy parse stopped after 0 pickle(s): unsupported pickle opcode 0x0 at 0. Unparsed content is unverified.

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 OpenVINO/Phi-4-mini-instruct-int4-ov

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.

architecturephi3 · 32 layers · 3072-dim
vocabulary200,064 tokens
licensemit
serializationno safetensors pickle custom code
chat templatepresent (chat_template.jinja) · sha256:7628a0569add8b8a
claimed lineagemicrosoft/Phi-4-mini-instruct
lineage verifiedunverified — weights battery pending
Full measured fingerprint
architecturesPhi3ForCausalLM
pipelinetext-generation
repo files21 — pickle: openvino_detokenizer.bin, openvino_model.bin, openvino_tokenizer.bin
revisione5813af02e85
HF snapshot865 downloads · 3 likes · updated 2026-07-06 · captured 2026-08-25
weights batterytoken-embedding scan n/a — no token-embedding tensor found in the pickle checkpoint(s) — pickle checkpoint(s) statically analyzed anyway
pickle auditopenvino_detokenizer.bin, openvino_model.bin, openvino_tokenizer.bin0 standard global(s) · legacy (pre-1.6) format, head-scan only
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-25 21:476s1
weights run 2026-08-25 measurements
probes runpickle-static-analysis

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/OpenVINO/Phi-4-mini-instruct-int4-ov/badge.svg)](https://ingot.tools/models/OpenVINO/Phi-4-mini-instruct-int4-ov)
Gate it in CI