Model page

Soheil-FM/deci-finetuned-3 warn

Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo; its license differs from its base model's. Plus 1 more issue.

downloads 16likes 0license otherarch llamaupdated 2023-10-13

claims base: Deci/DeciLM-6b-instruct · chat template: not found · 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 · 135 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 (adapter_model.bin, pytorch_model-00001-of-00002.bin, pytorch_model-00002-of-00002.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`).

medium License differs from claimed parent (other vs llama2,other)

This model declares other while its claimed base Deci/DeciLM-6b-instruct declares llama2,other. Verify the re-license is permitted before commercial use.

How to fix

Verify the re-license is actually permitted before relying on it.

  1. 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.
  2. If the re-license is not permitted, the parent's terms govern your use regardless of what this repo declares.

medium Undertrained (glitch) token surface in vocabulary

Embedding-norm scan flagged 135 undertrained tokens (norm < 0.3× the vocabulary median of 0.860), including 14 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "<0xFE>", "<0xFF>", "<0xFB>", "<0xFC>", "<0xFD>", "<0xFA>", "Mediabestanden", "oreferrer". 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-00002.bin, adapter_model.bin, pytorch_model-00002-of-00002.bin (no code executed) found only standard serialization globals (4 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 Deci/DeciLM-6b-instruct

Mean cosine similarity of 64 sampled token-embedding rows against Deci/DeciLM-6b-instruct 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 Soheil-FM/deci-finetuned-3

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,000 tokens
licenseother
serializationno safetensors pickle custom code
chat templatenone
claimed lineageDeci/DeciLM-6b-instruct
lineage verifiedconsistent vs Deci/DeciLM-6b-instruct — embedding-row cosine 1.000
glitch-token surface135 undertrained candidates, 14 plain-ASCII
Full measured fingerprint
architecturesDeciLMForCausalLM
librarytransformers
pipelinetext-generation
repo files15 — pickle: adapter_model.bin, pytorch_model-00001-of-00002.bin, pytorch_model-00002-of-00002.bin, training_args.bin
revisionf36f2b889090
HF snapshot15 downloads · 0 likes · updated 2023-10-13 · captured 2026-08-25
pickle auditpytorch_model-00001-of-00002.bin, adapter_model.bin, pytorch_model-00002-of-00002.bin — 4 standard global(s)
embedding tensormodel.embed_tokens.weight · F16 · 32,000×4096
embedding normsmedian 0.8604 · mean 0.8434
lineage checkconsistent — cosine 1 over 64 sampled rows vs Deci/DeciLM-6b-instruct
glitch-token samples"<0xFE>", "<0xFF>", "<0xFB>", "<0xFC>", "<0xFD>", "<0xFA>", "Mediabestanden", "oreferrer", "Normdaten", "demsel", "ITableView", "regnig"
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-25 22:2858s1
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 · 32,000×4096
glitch surface135 undertrained, 14 plain-ASCII
lineage checkconsistent — cosine 1 over 64 rows vs Deci/DeciLM-6b-instruct

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/Soheil-FM/deci-finetuned-3/badge.svg)](https://ingot.tools/models/Soheil-FM/deci-finetuned-3)
Gate it in CI