Model page

Aixile/Qwen-VL warn

Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo; no license declared — no usage rights by default. Plus 1 minor note.

downloads 16likes 1license none declaredarch qwenupdated 2023-09-27

chat template: not found · view on Hugging Face ↗

Scan coverageStatic battery2026-08-25Weights batteryqueuedBehavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-25
Weights batteryWeights forensics — no GPU, no downloadqueued
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 (pytorch_model-00001-of-00010.bin, pytorch_model-00002-of-00010.bin, pytorch_model-00003-of-00010.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.

medium No license declared

The model card declares no license. You have no usage rights by default — treat as all-rights-reserved until the owner clarifies.

How to fix

Get a license from the owner or pick a licensed alternative — this is a legal gap, not a technical one.

  1. With no declared license you have no usage rights by default; treat the weights as all-rights-reserved.
  2. Open an issue or discussion on the repo asking the owner to declare a license, or use the licensed upstream/parent model instead.

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

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 Aixile/Qwen-VL

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.

architectureqwen · 32 layers · 4096-dim
vocabulary151,936 tokens
licensenone declared
serializationno safetensors pickle custom code
chat templatenone
Full measured fingerprint
architecturesQWenLMHeadModel
librarytransformers
pipelinetext-generation
repo files22 — pickle: pytorch_model-00001-of-00010.bin, pytorch_model-00002-of-00010.bin, pytorch_model-00003-of-00010.bin, pytorch_model-00004-of-00010.bin, pytorch_model-00005-of-00010.bin, pytorch_model-00006-of-00010.bin, pytorch_model-00007-of-00010.bin, pytorch_model-00008-of-00010.bin, pytorch_model-00009-of-00010.bin, pytorch_model-00010-of-00010.bin
revision50e1e7476b37
HF snapshot16 downloads · 1 likes · updated 2023-09-27 · captured 2026-08-25
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightsqueued2026-08-25 22:210

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/Aixile/Qwen-VL/badge.svg)](https://ingot.tools/models/Aixile/Qwen-VL)
Gate it in CI