Alpha
Contact
Assess · MiniCPM5-1B

Can you own it?

Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input C ยท 56.8/100

This page is a projection of the one entry record, the Use & modify and Transparency factors that Assess 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

Intended & out-of-scope use

The publisher positions the model for "local assistants, coding agents, tool-use workflows, and reasoning scenarios where a compact model is preferred" and for "on-device, local deployment, and resource-constrained scenarios" (ev-card). The GitHub repository ships a desktop-pet demo that runs it locally (ev-github). The model is text-only. The card says generated content "should be reviewed and verified before use in high-stakes settings", so high-stakes decisions are out of scope without the deployer's own controls. Only English and Chinese are documented.

Known limitations, bias & failure modes

  • No safety evaluation exists. The card's only safety text says the model "may produce inaccurate, biased, or unsafe outputs" and leaves safeguards to the user (ev-card).
  • Benchmark rows are mixed. On the publisher's own table the model is behind LFM2.5-1.2B on GPQA-Diamond (26.26 vs 34.85), IFEval (80.41 vs 84.84), Multi-IF (43.54 vs 55.61) and MultiChallenge (19.48 vs 23.28). It is behind both Qwen baselines on BFCLv4 (25.15 vs 25.43 and 25.53) (ev-bench).
  • Capacity is small. A 1.08B model scores 48.85 on MMLU-Pro in that table, so expect weak factual recall and long-tail knowledge.
  • Only two languages are documented. The card lists English and Chinese, and nothing else is documented or evaluated.
  • The decay-phase pretraining tier was synthesised with MiniCPM4 and Qwen3 (ev-datasets), so the model carries those generators' errors and biases.

Openness tier & components

open_weights_recipe, as a judgement call between the 3 and 4 anchors. The open parts are Apache-2.0 weights at four stages (Base, SFT-only, final, plus official GGUF and MLX), a recipe description on the card, and three pretraining datasets. The card names the three datasets as the training corpus, and they are public and Apache-2.0 tagged on the Hub: Ultra-FineWeb, Ultra-FineWeb-L3 and UltraData-Math (ev-card, ev-datasets). That is more training data than most open-weight models release.

The closed parts are these. The SFT dataset UltraData-SFT-2605 sits behind an automatic Hub access gate and its card is unavailable (ev-sft-dataset). The synthesised RLVR data and the pairwise RLHF data are not linked. The repository holds user-side fine-tuning and quantisation scripts but no pretraining, RL or OPD pipeline and no evaluation harness (ev-github). There is no MiniCPM5 technical report, because the card's "Tech Report" link is the MiniCPM4 paper (ev-papers).

Components: weights open, licence open, training data partial, training code partial, evaluation partial, documentation partial.

License terms & permitted use

Apache License 2.0 for all MiniCPM5 checkpoints. The GitHub LICENSE file matches the canonical apache.org text line for line; only the copyright line differs ("Copyright [OpenBMB]"), so there is no field-of-use, scale, branding or registration clause (ev-license). The Hub metadata of the 1B and 2B families all reads apache-2.0 and ungated (ev-license-meta). Commercial use, modification, redistribution and sublicensing are permitted under the standard Apache terms (attribution, notice, patent grant and termination).

Two points matter. First, the LICENSE file is in the GitHub code repository. The Hub model repository has no LICENSE file and relies on the card sentence and metadata, so keep a copy of the GitHub file with any redistribution. Second, earlier MiniCPM generations (the 2B and V-2 era) have their weights under a custom General Model License that requires commercial authorisation by registration (ev-legacy-gml). The MiniCPM5 README replaces that with Apache-2.0. An older checkpoint carries different terms, so check before assuming this dossier applies.

The datasets are also Apache-2.0 tagged, but the Ultra-FineWeb card warns that its source datasets have their own licences (ev-datasets).

Supply-chain & provenance

The canonical source is huggingface.co/openbmb/MiniCPM5-1B, linked from the OpenBMB/MiniCPM GitHub README. The openbmb Hub org is not verified (isVerified: false), so identity rests on the GitHub cross-links and on Artificial Analysis attributing the model to OpenBMB (ev-repo-files, ev-aa).

Weights are a single safetensors shard with an LFS sha256, and there is no pickle file. The Hub's own scan reports no flagged files. There is no signature or attestation. Official GGUF (F16, Q8_0, Q4_K_M) and MLX 4-bit conversions come from the same org. Many community conversions exist, including repos named "Uncensored", which are uninspected.

On data lineage, Ultra-FineWeb-L3 was generated with MiniCPM4 and Qwen3, and the math selection used unnamed proprietary models (ev-datasets). The checkpoint checklist scores 5 of 8.

EU AI Act posture

The model is a general-purpose AI model. At 1.08B parameters it would need roughly 1.5 quadrillion training tokens to reach 1e25 FLOPs (6 x parameters x tokens), so it is not a systemic-risk model and no Article 55 package applies. Under Apache-2.0 with public weights it plausibly qualifies for the Article 53 open-source exemption from the Annex XI and XII documentation duties.

The surviving duties are a copyright policy and a public training-content summary. OpenBMB states no copyright policy and no EU-specific statement. The dataset cards are public and describe the pretraining sources, which partly serves as a training-content summary. The SFT card is gated, no pretraining token count is given, and the source-dataset licence caveat applies. Whether OpenBMB or Modelbest has signed the GPAI Code of Practice is unknown.

A deployer who fine-tunes and places the result on the EU market may become the provider for that derivative and should document the gaps above.

Benchmarks & evaluation

All numbers come from one publisher image on the model card (ev-bench). It covers Thinking mode only, against three small thinking-mode models (Qwen3-0.6B, Qwen3.5-0.8B, LFM2.5-1.2B), with no harness or prompt detail and no non-thinking results. The reported figures are an average of 42.57 against 35.61 for LFM2.5-1.2B, MATH-500 91.60, AIME-2025 and AIME-2026 both 40.42, LCB-v6 33.52, MMLU-Pro 48.85, tau2-Bench Telecom 79.53 and BFCLv4 25.15.

The card says the advantage is most visible in tool use, but on BFCLv4 the model is level with or below the Qwen baselines, so the tool-use lead rests on one benchmark. The comparison set has no Gemma, Llama, SmolLM, Granite or Qwen3-1.7B baseline. Artificial Analysis lists the model but publishes no score (ev-aa), and no other independent evaluation exists. The table is an unverified publisher claim, so run an evaluation on the deployer's own task.

How this scores

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

1

Use and modify freelyCan you run, modify and adapt it with no gate and no field-of-use trap?

Strong

Apache-2.0 across Base, SFT, final, GGUF and MLX checkpoints, ungated, with commercial use allowed and no field-of-use or registration clause.

How this scores (AOI sub-dimensions)
Openness4/5how much is released - weights, data, code, licence - and how freelyApache-2.0 weights at four checkpoint stages (Base, SFT, final, plus GGUF and MLX), a detailed card recipe, and three public Apache-2.0 pretraining datasets that the card names as the training corpus.
Legal3/5how permissive and clean the licence is for real commercial usePlain Apache-2.0 (identical to the canonical text apart from the copyright line), ungated, commercial use allowed, with no field-of-use or registration clause; the older General Model License is explicitly replaced.
2

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

Moderate

The recipe and three pretraining datasets are public, but the SFT dataset card is gated and unread, the RL data is partly unreleased, there is no MiniCPM5 report or training pipeline, and the benchmark table is an unverified image.

How this scores (AOI sub-dimensions)
Provenance3/5how well we can trace and verify what went into the modelSafetensors only (no pickle), Hub file scan clean, per-file LFS sha256, official GGUF and MLX conversions, and the GitHub repository links these exact Hub repos; checklist about 5 of 8.
Governance3/5how accountable and well-documented the publisher isAn identifiable, accountable publisher group (Modelbest, THUNLP, Renmin University) with a visible cadence since 2024 (MiniCPM 2B Feb 2024, MiniCPM3 Sep 2024, MiniCPM4 Jun 2025, MiniCPM5-1B May 2026, MiniCPM5-2B Sep 2026), an active repository (last push 2026-11-09), GitHub issue templates and Discussions.
What this means for adoptionUse of these weights is fully owned: Apache-2.0, ungated, runnable on a phone or laptop, with Base and SFT checkpoints and public pretraining data to adapt from. Ownership is partial because the reliability factor is weak: OpenBMB publishes no safety evaluation, policy or guard model. The SFT data card is gated, and the only benchmark is the publisher's own table. The model suits local assistants and fine-tuning behind the deployer's own guardrails and safety tests. Ownership moves to substantial once a safety evaluation exists.

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 LICENSE file in the OpenBMB/MiniCPM repository, which the MiniCPM5-1B model card links as the licence for "this repository and MiniCPM model weights", is the standard Apache License 2.0 text.
Licenceread2026-11-19
Hub card metadata for openbmb/MiniCPM5-1B, -SFT, -Base, -GGUF, -MLX and every MiniCPM5-2B checkpoint reads license apache-2.0 with gated false.
Licenceread2026-11-19
The legacy README for earlier MiniCPM generations says model weights "must strictly follow" a custom General Model License (GML), with commercial use needing authorisation from cpm@modelbest.cn by registration.
Model cardread2026-11-19
The MiniCPM5-1B model card describes a dense LlamaForCausalLM with 1,080,632,832 parameters, 24 layers, GQA with 16 query and 2 key-value heads, and a context length of 131,072.
Documentationread2026-11-19
The Hub repository holds one safetensors shard (2,161,290,912 bytes, LFS sha256 7ab8fd86...), no pickle and no LICENSE file.
Documentationread2026-11-19
The dataset cards for Ultra-FineWeb (about 1T English and 120B Chinese tokens), Ultra-FineWeb-L3 and UltraData-Math show that all three are public, ungated and Apache-2.0 tagged.
Documentationunverified2026-11-19
UltraData-SFT-2605 exists on the Hub (API metadata: gated auto, apache-2.0, 1,510 files, created 2026-05-21) but its card returns 401 "restricted ...
Technical_reportread2026-11-19
The card cites two arXiv papers.
Vendor announcementread2026-11-19
The publisher benchmark image on the model card (Thinking mode, three small baselines) reports an average of 42.57 vs Qwen3-0.6B 26.77, Qwen3.5-0.8B 25.14 and LFM2.5-1.2B 35.61.
Third-party analysisread2026-11-19
Artificial Analysis lists MiniCPM5-1B as an open-weights OpenBMB model, Apache 2.0, text only, 128k context, released 25 May 2026, with no publicly available API and no Intelligence Index score or other benchmark result on its model page.
Documentationread2026-11-19
The OpenBMB/MiniCPM repository holds a release log (MiniCPM5-1B 2026-05-19) and names the institutions (Modelbest, THUNLP, Renmin University GSAI).
Model cardread2026-11-19
The MiniCPM5-2B card (second model in the series, released 2026-09-07, Apache-2.0, ungated) lists a different and larger dataset set (adds UltraData-Code, UltraData-SFT-Agent-2609, UltraData-RL-2609, UltraX-Preview), so it is a separate release and is not scored in this entry.