LFM3-Omni-2B vs Nanbeige4.3-33B

LFM3-Omni-2B 40

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, files in the LiquidAI organisation, which Liquid's docs page for the model and its blog post link to (10). Safety evaluation 0, no safety results on the card or in Liquid's blog post for the LFM3 family, neither of which mentions safety testing. Agent guidance 0, Nothing on prompt injection, an instruction hierarchy, what refusals cover or safeguards to add. Licence risk 10, 15 less 5 for the $10M annual revenue threshold on commercial use. Security programme 0, no way to report a flaw found. 15 + 15 + 0 + 0 + 10 + 0 = 40.

Nanbeige4.3-33B 60

File safety earns 25, safetensors only and no repository code, so the card's trust_remote_code has nothing to run. Provenance earns 15, the lab's own organisation as its arXiv report links it, with a hash for every file. Safety evaluation earns 0 and agent guidance 0, since neither card says anything on either. Licence risk keeps all 15 under Apache 2.0. The security programme earns 5 for BOSS Zhipin's security response centre, which isn't linked to the model.

LFM3-Omni-2B 70

Chat template 20, chat_template.jinja in the repository (13,513 characters), with roles, images, video and audio, tools, deferred tools and tool results. Tool-calling format 25, the card and Liquid's tool-use page document tools passed through tools= in apply_chat_template, calls returned as XML and results sent back as tool messages. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so several calls fit in one turn, and the card documents tool calling from spoken or written requests. Structured output 0, the card doesn't mention JSON or structured output for this model. Reasoning control 0, the card says this is a non-reasoning model and that enable_thinking=True is not supported, so there is no thinking to turn off or budget. Context 5, 32K tokens of input and output per the card. 20 + 25 + 20 + 0 + 0 + 5 = 70.

Nanbeige4.3-33B 85

The chat template earns 20, Jinja in tokenizer_config.json. The tool-calling format earns 25, with the XML call format in the template and the qwen3_coder parser named for vLLM and SGLang. Trained tool calling earns 20, several calls per turn in the template. Structured output earns 0, as nothing mentions it. Reasoning control earns 10, thinking switched per request with the qwen3 reasoning parser named. Context earns 10 for 512K set in the config with no scaling.

LFM3-Omni-2B 49

Model card 14, Intended use (one on-device model in place of separate speech recognition, vision, language and speech models), architecture, parameters (2.17B), context (32K) and the text and speech languages. Training data 5, the card has no training section. Last change 20, the last commit, on 3 November 2026, changed the card's navigation icons, seven days before this check, and the one before it, on 28 October, documented video frame rate and frame limits. Responsiveness 0, none of the 12 discussions that aren't pull requests (27 October to 9 November 2026) has a reply from a LiquidAI member. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 5, the card gives a 32K context while config.json gives the language model 128,000 positions and Liquid's API lists 128,000 for the hosted model, so the card and the files don't agree on context. 14 + 5 + 20 + 0 + 5 + 5 = 49.

Nanbeige4.3-33B 56

The model card earns 11, with intended use, parameters, context and languages but no limitations, architecture or cut-off. Training data earns 0, as nothing describes it. Last change earns 20 for the quantised builds of 31 October 2026. Responsiveness earns 10, a Nanbeige member answering nine of 30 discussions. Version policy earns 5 for a first release, with a config change made and reverted under bare commit titles. File health earns 10, the files and the card agreeing.