Model page

GoldenLlama/krx_gemma2_9b_it warn

Weights only ship in a format that can run code when loaded; Chat template ends turns with <end_of_turn>, which is not a configured stop token.

downloads 12likes 0license gemmaarch gemma2updated 2024-10-16

claims base: unsloth/gemma-2-9b-it · 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-26256,000-token embedding scanned · 0 undertrained · lineage consistent · 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-00004.bin, pytorch_model-00002-of-00004.bin, pytorch_model-00003-of-00004.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 Chat template ends turns with <end_of_turn>, which is not a configured stop token

The chat template terminates assistant turns with <end_of_turn>, but the effective EOS set (config.json ∪ generation_config.json = [1] → ["<eos>"]) 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_of_turn>'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`).

  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.701). The glitch-token data-corruption class has no candidate surface in this model.

info Pickle static analysis clean

Opcode-level parse of pytorch_model-00001-of-00004.bin, pytorch_model-00002-of-00004.bin, pytorch_model-00003-of-00004.bin, pytorch_model-00004-of-00004.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.

info Weights consistent with claimed parent unsloth/gemma-2-9b-it

Mean cosine similarity of 64 sampled token-embedding rows against unsloth/gemma-2-9b-it is 1.000 — the weights plausibly descend from the declared base (relation: unspecified).

Put this result in your workflow

Check every checkpoint before it ships

Use the web app, API, CLI, or CI gate to scan candidate checkpoints and catch model drift before deployment. Public-model scans publish to the open database; paid plans add the volume needed for continuous checks.

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 GoldenLlama/krx_gemma2_9b_it

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.

architecturegemma2 · 42 layers · 3584-dim
vocabulary256,000 tokens
licensegemma
serializationno safetensors pickle
chat templatepresent · sha256:ecd6ae513fe103f0
claimed lineageunsloth/gemma-2-9b-it
lineage verifiedconsistent vs unsloth/gemma-2-9b-it — embedding-row cosine 1.000
glitch-token surfaceclean no undertrained tokens
Full measured fingerprint
architecturesGemma2ForCausalLM
pipelinetext-generation
repo files13 — pickle: pytorch_model-00001-of-00004.bin, pytorch_model-00002-of-00004.bin, pytorch_model-00003-of-00004.bin, pytorch_model-00004-of-00004.bin
revisioned64a91ff541
HF snapshot17 downloads · 0 likes · updated 2024-10-16 · captured 2026-08-25
pickle auditpytorch_model-00001-of-00004.bin, pytorch_model-00002-of-00004.bin, pytorch_model-00003-of-00004.bin, pytorch_model-00004-of-00004.bin — 3 standard global(s)
embedding tensormodel.embed_tokens.weight · F16 · 256,000×3584
embedding normsmedian 1.701 · mean 1.7215
lineage checkconsistent — cosine 1 over 64 sampled rows vs unsloth/gemma-2-9b-it
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-25 22:203m1
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 · F16 · 256,000×3584
glitch surface0 undertrained, 0 plain-ASCII
lineage checkconsistent — cosine 1 over 64 rows vs unsloth/gemma-2-9b-it

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