Documents

1 document, published on 8 Aug 2025. The chart runs from its publication to its latest known version; the table links to its page.

Zhipu AI'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.

Aug 2025GLM-4.5 technical report

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

Zhipu AI's documents, newest first.
DocumentPublishedKindVersions knownChangelogValues
GLM-4.5 technical reportTechnical report · 1 version known · Changelog: not applicable · 2 values8 Aug 2025Technical report1Not applicable2

Metric families reported

Zhipu AI's documents have a printed number in 1 of the 12 metric families: Harmful compliance and over-refusal.

Metric families in Zhipu AI's documents

Share of Zhipu AI's 1 document with at least one printed number in each metric family. A cell opens the data explorer at that family, filtered to Zhipu AI.

Share of each developer's documents in the version 0 dataset with at least one numeric value in each metric family.
DeveloperM1M2M3M4M5M6M7M8M9M10M11M12
Zhipu AI (1)0%0%0%0%0%0%100%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

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

Zhipu AI'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.

Zhipu AI's models, newest first by the date of each model's first card.
ModelFirst cardAvailabilityValues
GLM-4.5First card: 8 Aug 2025 · Public · 2 values8 Aug 2025Public2

Not recorded

No risk determinations are recorded from Zhipu AI's documents, and no safety framework is recorded for Zhipu AI.

No revisions are recorded: we have no record of a change made to one of Zhipu AI's documents after publication.

No restated values are recorded: no later Zhipu AI document is recorded as reporting an earlier model's result again.