DeepSeek
What the dataset holds from DeepSeek: its documents and their versions, the metric families they report, whether they keep a changelog, and any risk determinations, revisions and restated values recorded from them.
- Documents
- 1 · published on 17 Sep 2025
- Kinds
- 1 technical report
- Models
- 1
- Values
- 1
- Frameworks
- None recorded
- Its own index
- None recorded
Data as of 26 Sep 2026 · Dataset v0.1 · Methodology v0.1 · Changelog
Documents
1 document, published on 17 Sep 2025. The chart runs from its publication to its latest known version; the table links to its page.
DeepSeek's documents and the versions we know of
One row per document, from its publication to its latest dated version. A tick marks each later version whose date we know, from a changelog, a date in the document or our source registry.
| Document | Version | Date | Date known from | What changed |
|---|---|---|---|---|
| DeepSeek-R1 paper (Nature; arXiv v2) | Published | 17 Sep 2025 | our source registry | Not recorded |
| DeepSeek-R1 paper (Nature; arXiv v2) | Copy retrieved 26 Sep 2026 | 26 Sep 2026 | the date we retrieved it | Not recorded |
A copy we retrieved without knowing when that version was published has no tick: its only date is the day we read it. The table lists every version, with how its date is known. Versions known only from a changelog have no copy we hold yet.
Source: Safety Card Ledger v0.1 · Data from developer system cards · CC BY 4.0
| Document | Published | Kind | Versions known | Changelog | Values |
|---|---|---|---|---|---|
| DeepSeek-R1 paper (Nature; arXiv v2)Technical report · 1 version known · Changelog: not applicable · 1 value | 17 Sep 2025 | Technical report | 1 | Not applicable | 1 |
Metric families reported
None of DeepSeek's documents has a printed number in any metric family. Its only value is a statement in words.
Metric families in DeepSeek's documents
Share of DeepSeek's 1 document with at least one printed number in each metric family. A cell opens the data explorer at that family, filtered to DeepSeek.
| Developer | M1 | M2 | M3 | M4 | M5 | M6 | M7 | M8 | M9 | M10 | M11 | M12 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DeepSeek (1) | 0% | 0% | 0% | 0% | 0% | 0% | 0% | 0% | 0% | 0% | 0% | 0% |
Share of documents0%1-24%25-49%50-74%75-100%
- M1
- Evaluation awareness
- M2
- Reward hacking
- M3
- Sabotage and sandbagging
- M4
- Misalignment audits
- M5
- Honesty and hallucination
- M6
- Sycophancy
- M7
- Harmful compliance and over-refusal
- M8
- Jailbreak robustness
- M9
- Prompt injection
- M10
- Dangerous capabilities and risk determinations
- M11
- Self-preservation
- M12
- Chain-of-thought monitorability
The chart is already a table: every cell prints its share, and its label gives the two counts behind it. The CSV has the counts.
Read this as a lower bound: some documents were not read to the end in version 0 (each document's page says how far), so families reported late in them may be undercounted. Values read off a figure, stated in words, or given as a category do not count.
Source: Safety Card Ledger v0.1 · Data from developer system cards · CC BY 4.0
Changelog practice
A document has a changelog when it keeps its own record of the changes made to it after publication. Where it keeps none, changes can only be found by comparing its versions (Methodology §7).
DeepSeek's only document is marked as one to which a changelog does not apply.
- Not applicable
- Our source registry records a changelog as not applying to the document, for example a research paper or a launch post.
Models
1 model, newest first by the date of each model's first card.
| Model | First card | Availability | Values |
|---|---|---|---|
| DeepSeek-R1First card: 17 Sep 2025 · Public · 1 value | 17 Sep 2025 | Public | 1 |
Not recorded
No risk determinations are recorded from DeepSeek's documents, and no safety framework is recorded for DeepSeek.
No revisions are recorded: we have no record of a change made to one of DeepSeek's documents after publication.
No restated values are recorded: no later DeepSeek document is recorded as reporting an earlier model's result again.