GLM-5.3-Flash vs LFM3-Omni-2B

GLM-5.3-Flash 60

Memory earns nothing, since Z.ai's smallest build is the 328.4 GB FP8 one, about 394 GB with the fifth added, and neither Ollama nor LM Studio has a local build (both list it as cloud only). Four runtimes run it in a released version, llama.cpp, vLLM, SGLang and Transformers, for 20, while Ollama and LM Studio don't. Z.ai publishes one quantised build, FP8, for 10. The MIT licence with nothing added gives the full 15, the files download with no account or gate for 10, and Z.ai's own API plus six providers on Hugging Face serve it, for 5.

LFM3-Omni-2B 80

Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.29 GB projector file, and 1.39 GB × 1.2 = 1.7 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 10, Released llama.cpp has the lfm3 architecture with the LFM3 vision and audio projectors and speech output (src/models/lfm3.cpp and tools/mtmd at b12242, with a realtime client example), and Ollama's library has an lfm3-omni entry. Builds 15, Liquid's GGUF repository holds Q4_0, Q4_K_M, Q8_0, F16 and BF16 files, and Liquid publishes 4-bit and 8-bit MLX builds and an ONNX repository, all in the LiquidAI organisation. Terms 10, the LFM Open License v1.0, a custom licence that lets anyone use it commercially for free below a threshold of $10M annual revenue. Download 10, the Hub API reports gated false for the model and its GGUF, MLX and ONNX repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, Liquid's own API lists lfm3-omni-2b among its models, so the publisher hosts it. 30 + 10 + 15 + 10 + 10 + 5 = 80.

GLM-5.3-Flash 55

File safety is full, with safetensors only, no Python and no remote code needed in Transformers 5.16.1 or later. Provenance is full, files in the zai-org organisation Z.ai links from GitHub with a SHA-256 for every shard. Safety evaluation and agent guidance are 0, as nothing is published on either. Licence risk is the full 15, since MIT adds no policy, threshold or changeable terms. The security programme is 0, with no security.txt on z.ai or docs.z.ai, no SECURITY.md on GitHub and no advisories found.

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.

GLM-5.3-Flash 58

The card covers architecture, parameters and languages and misses four of the seven items, for 8. Training data is 5, a 30T-token corpus described with no sources or cut-off. The last change, a chat template speed-up on 15 October in both repositories, is within 30 days on 2 November, for 20; Z.ai's GLM-5 GitHub repository has changed only its docs since. Responsiveness is 10, as zai-org answered 14 of the 38 recent discussions others opened (26 August to 30 October), the last on 28 September, which is some but not most. Version policy is 5 for a first release, and file health is the full 10, with files and card agreeing and no broken-file report waiting as far as the research record shows.

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.