SemiAnalysis: Chinese AI Labs Rarely Publish Model Safety Test Results
Research firm SemiAnalysis has found that Chinese AI developers are extremely reluctant to share information about safety testing of their models. They have published almost no reports evaluating dangerous capabilities, even as concern about the risks of frontier systems grows worldwide. • Western labs release system cards and describe their risk evaluations. Chinese labs mostly stick to capability benchmarks. • The problem is more acute for open-weight models, whose safeguards are easy to strip out with fine-tuning after release. • Users and companies will have to test the models themselves.
AI-processed from 3DNews AI; edited by Hamidun News
Chinese AI developers almost never publish the results of their models' safety testing. That is the conclusion of research firm SemiAnalysis, which says labs in China are extremely reluctant to share how they test their systems for dangerous uses. The finding comes as concern grows worldwide over the rapid progress of frontier AI models. The material available to us contains no quantitative data from the report, but the conclusion itself matters: in a segment where labs compete for every percentage point on benchmarks, the risk section is most often left empty.
What is missing from the public record
Large Western labs have settled into a routine. A flagship model ships with a system card or model card describing dangerous-capability evaluations, red-team work, misuse testing results, and limitations. The contents of these documents can be disputed, but outside experts at least have material to check against. Chinese companies typically publish technical reports on architecture, training, and results on tests of knowledge, math, and coding. Sections on how a model behaves in biological, cyber, and other serious-risk scenarios are thin or missing entirely.
There are exceptions. In 2024, companies from several countries signed voluntary commitments at the Seoul AI Safety Summit, including China's Zhipu AI. But a commitment is not a report. Without a published methodology and results, there is no way to verify that it has been honored.
Why this hurts more for open models
A large share of the strongest Chinese models ship with open weights. For businesses that is an advantage: you can deploy a model in-house, fine-tune it, and avoid depending on an API. But openness has a downside. The safeguards a developer builds in can be removed through fine-tuning on a small budget. That makes pre-release risk evaluation, and an honest publication of its results, the only way to understand what the next people to pick up the model are starting from.
Independent testing has already turned up problems. In early 2025, Cisco researchers reported that DeepSeek R1 did not block a single harmful prompt from the HarmBench set in their test. The US institute NIST later published its own evaluation of DeepSeek, with findings on vulnerability to jailbreaking and agent hijacking. This kind of work is done by outside groups, not by the developers themselves, and that is exactly the asymmetry SemiAnalysis describes.
What the publication tells us
- Source of the finding: SemiAnalysis, a research firm specializing in AI and semiconductors.
- Core finding: Chinese developers are reluctant to disclose information about safety testing of their models.
- Context: global concern over the pace of frontier AI development.
- What the available excerpt does not include: a list of tested models, company names, and numerical scores.
What teams choosing a model should do
If you are building a Chinese model into a product, the absence of a public safety report means you will have to run the evaluation yourself. A minimal set looks like this: your own run on jailbreak prompts, a prompt injection test if the model has access to tools, and a check of the model's behavior on data from your industry. For agentic scenarios, restrict access permissions and keep an action log. For open-weight versions, add an external filtering layer on input and output rather than relying on built-in safeguards.
Ask vendors for documentation directly. If you get no answer, that is also data for your risk assessment. For the market as a whole, the question is simple: can disclosing safety test results become as standard as publishing benchmarks?
- Oct 24, 2026Moonshot AI Unveils Kimi K3.1 Pro, the First Pro Model in the Lineup, After the Kibitz Test
- Oct 24, 2026Nvidia in talks to buy Reflection AI, a startup valued at $8 billion
- Oct 24, 2026Open-weight models take 71.5% of Vercel AI Gateway tokens and 23% of spend
- Oct 23, 2026DeepSeek credits users with tokens as compensation after multi-hour outage
Key Questions Answered
What is missing from the public record?
Large Western labs have settled into a routine. A flagship model ships with a system card or model card describing dangerous-capability evaluations, red-team work, misuse testing results, and limitations. The contents of these documents can be disputed, but outside experts at least have material to check against. Chinese companies typically publish technical reports on architecture, training, and results on tests of knowledge, math, and coding. Sections on how a model behaves in biological, cyber, and other serious-risk scenarios are thin or missing entirely. There are exce
Why this hurts more for open models?
A large share of the strongest Chinese models ship with open weights. For businesses that is an advantage: you can deploy a model in-house, fine-tune it, and avoid depending on an API. But openness has a downside. The safeguards a developer builds in can be removed through fine-tuning on a small budget. That makes pre-release risk evaluation, and an honest publication of its results, the only way to understand what the next people to pick up the model are starting from. Independent testing has already turned up problems. In early 2025, Cisco researchers reported that DeepSe
What the publication tells us?
Source of the finding: SemiAnalysis, a research firm specializing in AI and semiconductors. Core finding: Chinese developers are reluctant to disclose information about safety testing of their models. Context: global concern over the pace of frontier AI development. What the available excerpt does not include: a list of tested models, company names, and numerical scores.
Build & Ship Production AI Apps with Vibe Coding
Join Zhemal Khamidun's hands-on Vibe Coding Intensive at hamidun.com/vibecoding — master Claude Code, Cursor, and autonomous agentic workflows.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.