LFM2.5-2.6B vs LongCat-2.5

LFM2.5-2.6B 90

Memory earns the full 30, since Liquid's own 4-bit GGUF is 1.59 GB and fits 8 GB with room to spare. Runtimes earn 25, with the lfm2 architecture in released llama.cpp, vLLM, SGLang and Transformers, and in Ollama through the llama.cpp version it pins. Builds earn 15 for Liquid's own GGUF, MLX and ONNX builds at many precisions. Terms earn 10, a custom licence that is free for commercial use under $10M of annual revenue. Download earns 10, with no gate. Hosted earns nothing, as Hugging Face maps no inference provider and Liquid's docs list no hosted API for it.

LongCat-2.5 35

Memory 0, the smallest build is Meituan's W4A4 repository, 1,336 GB, and 1,336 GB × 1.2 = 1,603 GB, far above 256 GB. The BF16 files are 3,562 GB. Runtimes 0, none of the six runs it in a released version: vLLM 0.33.0, SGLang 0.5.23, Transformers 5.22.2 and llama.cpp b12242 have no LongcatCausalLM or pro_v code, and the model code config.json names isn't in the repository. Builds 10, one quantised build from Meituan, the W4A4 repository (4-bit experts, 1,336 GB). Terms 15, MIT in the metadata, the LICENSE file and the card, with nothing added. Download 10, the Hub API reports gated false for both repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it. 0 + 0 + 10 + 15 + 10 + 0 = 35.

LFM2.5-2.6B 57

The model card earns 17, with everything but a knowledge cut-off. Training data earns 5 for a general description without a cut-off. The last change earns 20, a card commit on 3 November 2026 naming LFM3-1.7B as the new version. Responsiveness earns 5, with Liquid replies in 2 of 16 discussions. Version policy earns 5, as Liquid now lists the model as deprecated with a replacement but no date. File health earns 5, since the files agree but a report about the card waits without a reply.

LongCat-2.5 46

Model card 11, Intended use, limitations (the usage considerations), the architecture and the parameter counts are on the card. Training data 5, A general description of the training stages and where the reinforcement learning tasks came from, with no sources, sizes or cut-off. Last change 20, the last commit, on 10 November 2026, updated the card, on the day of this check. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (9 and 10 November 2026) has a reply from a meituan-longcat member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, LongCat-2.0 stays in its own repositories and 2.5 came out in new ones, with no dated note on the older ones that we read. File health 5, the template is in both places and agrees, but config.json's auto_map names configuration_longcat_oe and modeling_longcat_oe, which aren't in the repository, and the tokenizer config's 131,072-token length is a quarter of the config's 524,288 positions. 11 + 5 + 20 + 0 + 5 + 5 = 46.

LFM2.5-2.6B 50

File safety earns 25, safetensors and GGUF only, and nothing from the repository runs to load it or build prompts. Provenance earns 15, files in the LiquidAI organisation Liquid links to, with a checksum for every file. Safety evaluation and agent guidance earn nothing, since Liquid publishes neither. Licence risk earns 10, losing 5 for the revenue threshold, with no use policy and no change since release. The security programme earns nothing, since no security.txt, disclosure policy or security contact was found.

LongCat-2.5 60

File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in the meituan-longcat organisation, the name of Meituan's GitHub organisation that the card links for deployment, and the card's licence names Meituan (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions under Usage Considerations: not evaluated for every use, assess accuracy, safety and fairness before sensitive use, and follow the law. Licence risk 15, MIT with no use policy, no threshold and no right to change the terms. Security programme 0, no way to report a flaw on the card beyond a general contact, and Meituan's own security pages weren't looked up, so this scores as absent and is an open question. 25 + 15 + 0 + 5 + 15 + 0 = 60.