Model page

mikecovlee/tinymixtral-v1.0 warn

Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo. Plus 1 minor note.

downloads 138likes 1license mitarch tinymixtralupdated 2026-07-17

chat template: present · view on Hugging Face ↗

Scan coverageStatic battery2026-08-26Weights battery2026-08-26Behavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-26
Weights batteryWeights forensics — no GPU, no downloadcomplete 2026-08-2632,000-token embedding scanned · 0 undertrained · pickle audit clean
Behavioral batteryLive-inference differentialsnot run

Ingot runs three batteries against a model. What each one checks →

Findings

Scanned 2026-08-26 · published from a community scan.

medium Pickle-serialized weights, no safetensors

Weights ship only as pickle-based files (pytorch_model.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`).

info Embedding-norm glitch scan clean

No undertrained tokens found: every non-special token's embedding norm is above 0.3× the vocabulary median (1.513). The glitch-token data-corruption class has no candidate surface in this model.

info Pickle static analysis clean

Opcode-level parse of pytorch_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 mikecovlee/tinymixtral-v1.0

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-26.

architecturetinymixtral · 10 layers · 896-dim
vocabulary32,000 tokens
licensemit
serializationno safetensors pickle custom code
chat templatepresent (chat_template.jinja) · sha256:66291cf0045c2425
glitch-token surfaceclean no undertrained tokens
Full measured fingerprint
architecturesTinyMixtralForCausalLM
librarytransformers
pipelinetext-generation
repo files12 — pickle: pytorch_model.bin
revisionffd87a1fde3c
HF snapshot138 downloads · 1 likes · updated 2026-07-17 · captured 2026-08-25
pickle auditpytorch_model.bin3 standard global(s)
embedding tensorembed_tokens.weight · F32 · 32,000×896
embedding normsmedian 1.5131 · mean 1.6071
lineage checkno claimed base model
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-25 21:5125s1
weights run 2026-08-25 measurements
probes runglitch-norm-scan, zero-template-token-scan, pickle-static-analysis, lineage-norm-correlation
embedding tensorembed_tokens.weight · F32 · 32,000×896
glitch surface0 undertrained, 0 plain-ASCII
lineage checknot checked (no claimed base model)

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/mikecovlee/tinymixtral-v1.0/badge.svg)](https://ingot.tools/models/mikecovlee/tinymixtral-v1.0)
Gate it in CI