Alpha
Contact
Support · DeepSeek-R1-Distill

Will it last?

Ownership levelSubstantialnone·limited·partial·substantial·fullAnalytical input C ยท 64.8/100

This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.

Which domain expands which factor
  • AssessUse & modify + Transparency
  • ImplementData control + Reliability
  • UseReliability
  • SupportTransparency

Common problems & fixes

The recurring issues are reasoning (think-tag) parsing in the client, quant-quality trade-offs at the smallest sizes, and confusing a distil with the full R1. The list is not exhaustive. The large community around these consumer-runnable models is the practical first stop.

Versions, changelog & cadence

The R1-Distill-Qwen sizes are published on the verified deepseek-ai organisation. There is no formal changelog document; the Hugging Face revision hash is the changelog anchor.

Security / vulnerability disclosure

No formal vulnerability-disclosure or security policy is published. The only contact is the general deepseek-ai org presence. This is a gap, so build it into your own incident-response plan.

Community & support channels

The deepseek-ai Hugging Face organisation and GitHub, plus a very large community ecosystem around these consumer-runnable distils.

Deprecation / end-of-life policy

No deprecation or end-of-life policy is published for the distil checkpoints. Older revisions remain downloadable, but no sunset commitment is documented. This is a gap.

Tracked known issues

The standing issues are the absence of safety tuning, China-aligned censorship carried over from R1, and quant-quality trade-offs at the smallest sizes. See Assess for the detail.

How this scores

The ownership factor this domain covers, drawn from the one entry record.

2

TransparencyDo you know what it is: weights, training, behaviour, and legible terms?

Moderate

Weights are inspectable under the MIT licence, but the distillation data and code are closed and the weights carry R1's China-aligned topic filtering, which cannot be inspected. Open-weights tier, so moderate.

How this scores (AOI sub-dimensions)
Provenance3/5how well we can trace and verify what went into the modelVerified deepseek-ai org on Hugging Face, safetensors with checksums, a clear canonical source and no malicious-checkpoint incident (checklist ~5/8).
Governance3/5how accountable and well-documented the publisher isActive, named publisher (DeepSeek) with a verified org and technical reports, meeting the score-3 anchor.
What this means for adoptionYou substantially own these self-hosted MIT-licensed R1-Distill (Qwen) models. The permissive licence makes use-and-modify strong, and self-hosting, including on-device at the small sizes, keeps your data yours, so data-control is strong too. Ownership stops short of full because the distillation data and code are closed (not reproducible) and the weights carry R1's China-aligned filtering and no safety tuning of their own. Deploy behind your own guardrails.

Sources

The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.

Licenceread2026-11-19
The R1-Distill-Qwen repositories (1.5B, 7B, 14B, 32B) carry DeepSeek's MIT LICENSE, and the card metadata declares license mit.
Model cardread2026-11-19
The model cards on the verified deepseek-ai Hugging Face org describe dense 1.5B, 7B, 14B and 32B models distilled from R1, with a 128K context (from the Qwen2.5 bases) and safetensors weights.
Third-party analysisunverified2026-08-03
On public leaderboards the R1-Distill-Qwen-14B and 32B are strong reasoning models for their size; the 1.5B is modest.
Third-party analysisunverified2026-08-03
The R1-Distill checkpoints are research distils with no safety tuning of their own.
Third-party analysisunverified2026-08-03
The R1-Distill-Qwen checkpoints (1.5B-32B) are well below the systemic-risk threshold.