Model page

sudeshmu/fine_tune warn

Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo; the chat template was dropped from its base model, which changes behavior. Plus 2 more issues.

downloads 272likes 9license mitarch mor_llamaupdated 2025-08-28

claims base: microsoft/DialoGPT-medium · chat template: not found · view on Hugging Face ↗

Scan coverageStatic battery2026-08-25Weights batteryfailedBehavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-25
Weights batteryWeights forensics: no GPU, no downloadfailed429 Too Many Requests for https://huggingface.co/api/models/sudeshmu/fine_tune
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.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 Chat template dropped vs parent

microsoft/DialoGPT-medium ships a chat template; this repo does not. Serving stacks will silently fall back to a generic template, changing behavior. (In our 296-model census, 78% of pure quantization re-releases changed or dropped the template.)

How to fixingot patch

Restore the parent's chat template in `tokenizer_config.json` — a pure metadata fix.

  1. Run `ingot patch <owner/model>` — the patch manifest carries the parent's template and applies it to a local copy's `tokenizer_config.json`.
  2. Or fix by hand: copy the `chat_template` value from the parent repo's `tokenizer_config.json` into this model's, and pin your serving stack to that file.
  3. If the drift was intentional (the author retrained on a new template), confirm that in the model card before "fixing" it — restoring the parent template on retrained weights changes behavior too.

medium Architecture differs from claimed parent (mor_llama vs gpt2)

This model declares microsoft/DialoGPT-medium as its base, but its config declares architecture 'mor_llama' while the parent is 'gpt2'. A finetune, merge, or quantization cannot change the architecture family — the lineage label is wrong or misleading, so treat provenance claims (training data, safety posture, licensing) as unverified.

How to fix

Fix or verify the `base_model` declaration so lineage checks can run.

  1. If you own the repo: correct the `base_model` field in the model card metadata to the real, public parent.
  2. If you don't: identify the true parent (config architecture + weight shapes narrow it fast) and re-scan with that lineage in mind.

medium Vocabulary size differs from claimed parent (49152 vs 50257)

A changed vocab means changed tokenization: strings will split differently than on microsoft/DialoGPT-medium, which can shift behavior on identifiers, codes, and non-English text.

How to fixweight-level

Not patchable: the vocab size mirrors the embedding matrix in the weights. Verify the change was intentional.

  1. Do not edit `vocab_size` in config.json to "match the parent" — it must equal the embedding table in the shipped weights or the model won't load.
  2. Diff the tokenizers (`tokenizer.json` / added_tokens) against the parent to see what was added or removed, and test your own identifiers, codes, and non-English text through both.
  3. If the drift is unexplained by the model card, treat tokenization-sensitive behavior as unvalidated on this model.
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 sudeshmu/fine_tune

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.

architecturemor_llama · 32 layers · 960-dim
vocabulary49,152 tokens
licensemit
serializationno safetensors pickle custom code
chat templatenone
claimed lineagemicrosoft/DialoGPT-medium
lineage verifiedunverified — weights battery pending
Full measured fingerprint
architecturesMoRLlamaForCausalLM
librarytransformers
pipelinetext-generation
repo files8 — pickle: pytorch_model.bin
revision6c53489d32a1
HF snapshot72 downloads · 9 likes · updated 2025-08-28 · captured 2026-08-25

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