TIGER-Lab/VLM2Vec-LoRA warn
Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo; Chat template ends turns with <|end|>, which is not a configured stop token. Plus 1 more issue.
claims base: microsoft/Phi-3.5-vision-instruct · chat template: present · view on Hugging Face ↗
Scan coverageStatic battery2026-08-25Weights battery2026-08-25Behavioral batterynot rundetails
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-25 |
| Weights battery | Weights forensics — no GPU, no download | complete 2026-08-25no token vocabulary — pickle audit only · pickle audit clean |
| 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 (adapter_model.bin, training_args.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.
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.
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 = [2] → ["</s>"]) 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 microsoft/Phi-3.5-vision-instruct 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.
info Pickle static analysis clean
Opcode-level parse of adapter_model.bin (no code executed) found only standard serialization globals (3 distinct, all torch/collections/numpy). Pickle remains an executable format — this verifies the current bytes, not future uploads; prefer a safetensors release.
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 TIGER-Lab/VLM2Vec-LoRA
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 | phi3_v · 32 layers · 3072-dim |
| vocabulary | 32,064 tokens |
| license | apache-2.0 |
| serialization | no safetensors pickle custom code |
| chat template | present · sha256:79e4ca4b7d902dc7 |
| claimed lineage | microsoft/Phi-3.5-vision-instruct |
| lineage verified | unverified — weights battery pending |
Full measured fingerprint
| architectures | Phi3VForCausalLM |
| library | transformers |
| pipeline | text-generation |
| repo files | 163 — pickle: adapter_model.bin, training_args.bin |
| revision | 3161a2bb24da |
| HF snapshot | 433 downloads · 11 likes · updated 2025-07-13 · captured 2026-08-25 |
| weights battery | token-embedding scan n/a — no token-embedding tensor found in the pickle checkpoint(s) — pickle checkpoint(s) statically analyzed anyway |
| pickle audit | adapter_model.bin — 3 standard global(s) |
Battery runs (1)the run trace behind the findings — what each job measured
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | complete | 2026-08-25 21:48 | 3s | 1 |
weights run 2026-08-25 — measurements
| probes run | pickle-static-analysis |
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/TIGER-Lab/VLM2Vec-LoRA)