LFM3-VL-2B vs SmolLM3-3B

LFM3-VL-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.

SmolLM3-3B 65

File safety 25, safetensors only and nothing from the repository runs on load or to build prompts. Provenance 15, the HuggingFaceTB organisation linked from Hugging Face's launch post, with a SHA-256 for each shard. Safety evaluation 0, none published. Agent guidance 5, only the general cautions in the card's Limitations section. Licence risk 15, Apache 2.0 with nothing added and a working licence link. Security programme 5, huggingface.co has a valid security.txt and Transformers has a security policy; whether advisories are handled in public couldn't be checked from our session, so that half is scored as absent.

LFM3-VL-2B 90

Chat template 20, chat_template.jinja in the repository (12,129 characters), with roles, images and video, tools, deferred tools, tool results and the thinking switch. 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 says its fine-tuning mix included tool calling and agentic traces. Structured output 5, the card's vLLM and SGLang commands set a structured-output backend and its fine-tuning table has a JSON extraction notebook, but nothing says how to ask this model for JSON. Liquid's API guide documents response_format with lfm3-1.7b as its example. Reasoning control 10, Liquid's chat-template page documents enable_thinking=False in apply_chat_template for LFM3, with reasoning on by default inside think tags, and the card documents preserve_thinking and reports a no-thinking configuration in its benchmarks. Context 10, 128K tokens of input and output per the card, and max_position_embeddings 128000 for the language model in config.json. 20 + 25 + 20 + 5 + 10 + 10 = 90.

SmolLM3-3B 80

Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card says how tools are declared, how calls come back and which vLLM parser to use. Trained tool calling 20, the template invites one or more calls per turn, each in its own block. Structured output 0, nothing documents asking the weights for JSON. Reasoning control 10, thinking turns off per request through the kwarg or a system-prompt flag, and the reasoning comes back in think tags. Context 5, trained at 65,536 tokens, with 131,072 only through YaRN.