Model page

huihui-ai/DeepSeek-R1-Distill-Qwen-7B-abliterated-v2 warn

downloads 334likes 55license none declaredarch qwen2params 7615.6Mupdated 2025-02-16

claims base: deepseek-ai/DeepSeek-R1-Distill-Qwen-7B · chat template: present · view on Hugging Face ↗

Scan coverage

Ingot runs three batteries against a model. What each one checks →

BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics — no GPU, no downloadcomplete 2026-08-21152,064-token embedding scanned · 14086 undertrained · lineage consistent
Behavioral batteryLive-inference differentialsnot run

Findings

Scanned 2026-08-21 · published from a community scan.

medium No license declared

The model card declares no license. You have no usage rights by default — treat as all-rights-reserved until the owner clarifies.

How to fix

Get a license from the owner or pick a licensed alternative — this is a legal gap, not a technical one.

  1. With no declared license you have no usage rights by default; treat the weights as all-rights-reserved.
  2. Open an issue or discussion on the repo asking the owner to declare a license, or use the licensed upstream/parent model instead.

medium Chat template differs from claimed parent

The chat template does not match deepseek-ai/DeepSeek-R1-Distill-Qwen-7B's. Template drift silently changes model behavior even when weights are identical — 37% of drifted derivatives in our census left it undisclosed. Diff the templates before deploying.

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

Embedding-norm scan flagged 14086 undertrained tokens (norm < 0.3× the vocabulary median of 1.160), including 3462 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "TokenNameIdentifier", "ForCanBeConverted", "ForCanBeConvertedToF", "$PostalCodesNL", "<unk>", "useRalative", "useRal", "Cumhurba". 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 Weights consistent with claimed parent deepseek-ai/DeepSeek-R1-Distill-Qwen-7B

Mean cosine similarity of 64 sampled token-embedding rows against deepseek-ai/DeepSeek-R1-Distill-Qwen-7B is 1.000 — the weights plausibly descend from the declared base (relation: unspecified).

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.

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-21.

architectureqwen2 · 28 layers · 3584-dim
parameters7615.6M
vocabulary152,064 tokens
licensenone declared
serializationsafetensors
chat templatepresent · sha256:b6835114b7303ddd
claimed lineagedeepseek-ai/DeepSeek-R1-Distill-Qwen-7B
lineage verifiedconsistent vs deepseek-ai/DeepSeek-R1-Distill-Qwen-7B — embedding-row cosine 1.000
glitch-token surface14,086 undertrained candidates, 3,462 plain-ASCII
Full measured fingerprint
architecturesQwen2ForCausalLM
librarytransformers
pipelinetext-generation
repo files13
revision03f2ebe6efc0
HF snapshot332 downloads · 55 likes · updated 2025-02-16 · captured 2026-08-21
embedding tensormodel.embed_tokens.weight · BF16 · 152,064×3584
embedding normsmedian 1.1598 · mean 1.0362
lineage checkconsistent — cosine 1 over 64 sampled rows vs deepseek-ai/DeepSeek-R1-Distill-Qwen-7B
glitch-token samples"TokenNameIdentifier", "ForCanBeConverted", "ForCanBeConvertedToF", "$PostalCodesNL", "<unk>", "useRalative", "useRal", "Cumhurba", "webElementX", "NdrFc", "_ComCallableWrapper", "NdrFcShort"

Battery runs

The run trace behind the findings above: every deep-battery job for this model, with what each run measured or why it failed. Findings are only as good as the runs that produced them.

batterystatusqueueddurationattempts
weightscomplete2026-08-21 05:153m1
weights run 2026-08-21 measurements
probes runglitch-norm-scan, lineage-norm-correlation
embedding tensormodel.embed_tokens.weight · BF16 · 152,064×3584
glitch surface14,086 undertrained, 3,462 plain-ASCII
lineage checkconsistent — cosine 1 over 64 rows vs deepseek-ai/DeepSeek-R1-Distill-Qwen-7B

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 huihui-ai/DeepSeek-R1-Distill-Qwen-7B-abliterated-v2

Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the 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/huihui-ai/DeepSeek-R1-Distill-Qwen-7B-abliterated-v2/badge.svg)](https://ingot.tools/models/huihui-ai/DeepSeek-R1-Distill-Qwen-7B-abliterated-v2)
Gate it in CI