Model page

WhiteRabbitNeo/WhiteRabbitNeo-7B-v1.5a warn

Weights only ship in a format that can run code when loaded; EOS ids disjoint between config.json and generation_config.json; glitch tokens that can silently corrupt ordinary input.

Could not load this model from the Hugging Face API (private, gated, or nonexistent). Findings below are from our archive.

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,256-token embedding scanned · 1083 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-00001-of-00003.bin, pytorch_model-00002-of-00003.bin, pytorch_model-00003-of-00003.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 EOS ids disjoint between config.json and generation_config.json

config.json declares eos_token_id [32023] while generation_config.json declares [32014] with no overlap. Runtimes read one or the other, so at least one of them stops generation on the wrong token (or never). Align both files on the token the chat template actually ends turns with.

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 Undertrained (glitch) token surface in vocabulary

Embedding-norm scan flagged 1083 undertrained tokens (norm < 0.3× the vocabulary median of 8.875), including 343 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "milions", "anys", "desocupats", "persones", "unipersonals", "capbaix", "corresponia", "solteres". In models where this class was tested behaviorally, such tokens silently rewrote user input into confident, schema-valid, wrong output. These are candidates from the weights alone; behavioral confirmation requires the behavioral battery.

How to fixruntime guardweight-level

Keep the affected token strings out of the model's input — the scan-derived runtime guard carries this model's exact blocklist.

  1. Fetch this model's guard artifact (`/api/v1/guard/<owner>/<model>`): the confirmed corrupting tokens and the low-norm candidate list, derived from the published scan.
  2. Screen inbound text with it (the `@ingotai/guard` package is a reference implementation) and route flagged records to a different model or human review — verbatim-copy tasks on flagged strings are the failure mode.
  3. The underlying cause is undertrained embeddings in the weights; a true fix is weight-level (continued pretraining on the affected tokens) — that is not a patch, it's a training job.

info Pickle static analysis clean

Opcode-level parse of pytorch_model-00001-of-00003.bin, pytorch_model-00002-of-00003.bin, pytorch_model-00003-of-00003.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 WhiteRabbitNeo/WhiteRabbitNeo-7B-v1.5a

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.

architecturellama · 32 layers · 4096-dim
vocabulary32,256 tokens
licenseother
serializationno safetensors pickle
chat templatenone
glitch-token surface1,083 undertrained candidates, 343 plain-ASCII
Full measured fingerprint
architecturesLlamaForCausalLM
librarytransformers
pipelinetext-generation
repo files11 — pickle: pytorch_model-00001-of-00003.bin, pytorch_model-00002-of-00003.bin, pytorch_model-00003-of-00003.bin
revisionbaef600fd358
HF snapshot245 downloads · 51 likes · updated 2024-03-10 · captured 2026-08-25
pickle auditpytorch_model-00001-of-00003.bin, pytorch_model-00002-of-00003.bin, pytorch_model-00003-of-00003.bin3 standard global(s)
embedding tensormodel.embed_tokens.weight · BF16 · 32,256×4096
embedding normsmedian 8.8749 · mean 8.5855
lineage checkno claimed base model
glitch-token samples"milions", "anys", "desocupats", "persones", "unipersonals", "capbaix", "corresponia", "solteres", "Naixements", "llogaters", "habitants", "unidenc"
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-25 21:4948s1
weights run 2026-08-25 measurements
probes runglitch-norm-scan, zero-template-token-scan, pickle-static-analysis, lineage-norm-correlation
embedding tensormodel.embed_tokens.weight · BF16 · 32,256×4096
glitch surface1,083 undertrained, 343 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/WhiteRabbitNeo/WhiteRabbitNeo-7B-v1.5a/badge.svg)](https://ingot.tools/models/WhiteRabbitNeo/WhiteRabbitNeo-7B-v1.5a)
Gate it in CI