Model page

deepseek-ai/DeepSeek-R1 warn

Loading it runs custom code from the repo; glitch tokens that can silently corrupt ordinary input.

downloads 994.2klikes 14.3klicense mitarch deepseek_v3params 684489.8Mupdated 2025-03-27

chat template: present · view on Hugging Face ↗

Scan coverageStatic battery2026-08-20Weights battery2026-08-20Behavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-20
Weights batteryWeights forensics: no GPU, no downloadcomplete 2026-08-20129,280-token embedding scanned · 607 undertrained
Behavioral batteryLive-inference differentialsnot run

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

Findings

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

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

Embedding-norm scan flagged 607 undertrained tokens (norm < 0.3× the vocabulary median of 3.196), including 59 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "kabungtor", "unisipyo", "ultatua", "pagklas", "jeftigelse", "bingkil", "nahimut", "asarangang". 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.

Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the 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.

Fingerprint

The durable profile of this model: measured weights-and-metadata facts, rebuilt on every scan and battery run. Updated 2026-08-20.

architecturedeepseek_v3 · 61 layers · 7168-dim
parameters684531.4M
vocabulary129,280 tokens
licensemit
serializationsafetensors custom code
chat templatepresent · sha256:563b1ce7d61d50a9
glitch-token surface607 undertrained candidates, 59 plain-ASCII
Full measured fingerprint
architecturesDeepseekV3ForCausalLM
librarytransformers
pipelinetext-generation
repo files174
revision56d4cbbb4d29
HF snapshot6.4M downloads · 13.6k likes · updated 2025-03-27 · captured 2026-08-20
embedding tensormodel.embed_tokens.weight · BF16 · 129,280×7168
embedding normsmedian 3.196 · mean 3.1572
lineage checkno claimed base model
glitch-token samples"kabungtor", "unisipyo", "ultatua", "pagklas", "jeftigelse", "bingkil", "nahimut", "asarangang", "Pagklas", "ugnawan", "Kadaghan", "unoang"
Battery runs (3)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-20 18:0274s1
weightscomplete2026-08-20 08:1069s1
weightscomplete2026-08-20 06:3476s1

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