Model page

hipnologo/falcon-7b-instruct-qlora-truthful-qa warn

Weights only ship in a format that can run code when loaded; loading it runs custom code from the repo; EOS ids disjoint between config.json and generation_config.json. Plus 1 more issue.

downloads 12likes 2license apache-2.0arch RefinedWebModelupdated 2023-09-22

claims base: vilsonrodrigues/falcon-7b-instruct-sharded · chat template: not found · view on Hugging Face ↗

Scan coverageStatic battery2026-08-25Weights batteryqueuedBehavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-25
Weights batteryWeights forensics — no GPU, no downloadqueued
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 (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.

medium EOS ids disjoint between config.json and generation_config.json

config.json declares eos_token_id [11] while generation_config.json declares [2] 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 Architecture differs from claimed parent (RefinedWebModel vs falcon)

This model declares vilsonrodrigues/falcon-7b-instruct-sharded as its base, but its config declares architecture 'RefinedWebModel' while the parent is 'falcon'. 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.

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 hipnologo/falcon-7b-instruct-qlora-truthful-qa

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.

architectureRefinedWebModel · 32 layers · 4544-dim
vocabulary65,024 tokens
licenseapache-2.0
serializationno safetensors pickle custom code
chat templatenone
claimed lineagevilsonrodrigues/falcon-7b-instruct-sharded
lineage verifiedunverified — weights battery pending
Full measured fingerprint
architecturesRWForCausalLM
librarypeft
pipelinetext-generation
repo files12 — pickle: adapter_model.bin, pytorch_model-00001-of-00002.bin, pytorch_model-00002-of-00002.bin
revision6bf5e96a6186
HF snapshot12 downloads · 2 likes · updated 2023-09-22 · captured 2026-08-25
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightsqueued2026-08-25 22:410

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/hipnologo/falcon-7b-instruct-qlora-truthful-qa/badge.svg)](https://ingot.tools/models/hipnologo/falcon-7b-instruct-qlora-truthful-qa)
Gate it in CI