Darwin-36B-Opus vs LFM3-Audio-2B

Darwin-36B-Opus 55

File safety 25, safetensors and GGUF only with no code in the repository, so the card's trust_remote_code flag loads nothing extra. Provenance 15, the files are in the FINAL-Bench organisation that vidraft.net links to, with a SHA-256 for every weight file. Safety evaluation 0 and agent guidance 0, nothing published. Licence risk 15, Apache 2.0 through the whole chain with no conditions added. Security programme 0, no security.txt, policy or contact.

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

Darwin-36B-Opus 70

Chat template 20, Qwen3.6's Jinja template in the repository. Tool-calling format 10, the format is only in the template and the card says nothing about tools. Trained tool calling 20, inherited from the base that was trained for it, with several calls in one turn in the template, though the publisher neither claims nor tests it. Structured output 0. Reasoning control 10, the template turns thinking off per request and the card shows where the reasoning comes back. Context 10, 262,144 tokens.

LFM3-Audio-2B 85

Chat template 20, chat_template.jinja in the repository (9,328 characters), with roles, 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 names turning spoken requests into tool calls as one of its four uses. Structured output 5, the card says the model is designed for structured outputs without saying how to ask for JSON. Liquid's API guide documents response_format with lfm3-1.7b as its example. Reasoning control 10, the card documents reasoning per request for text replies: the caller prefills the assistant turn with an open think tag to let the model reason, or a closed one for a direct answer, with a use_thinking example. Context 5, 32K tokens of input and output per the card. 20 + 25 + 20 + 5 + 10 + 5 = 85.

Darwin-36B-Opus 61

Model card 11, it covers architecture, parameters, context and languages but not intended use, limitations or a knowledge cut-off. Training data 5, the reasoning parent's fine-tune is described without datasets or a cut-off. Last change 20, on 1 November 2026 the publisher added a LICENSE file and a corrected eval_results note to the main repository and edited the POCKET-35B-GGUF card, read as this run reads card edits on other open-weight listings (Muse Glimmer 30B, MiMo-V2.6 Distill Qwen 9B, Apertus v1.5 8B). The weights date from 23 April and the GGUF build from 22 July. Responsiveness 20, the publisher answered 8 of the 13 discussions, and two of the rest are its own posts. Version policy 5, a first release whose weights were replaced twice in its first day with commit titles but no card note. File health 0, the card's head counts and base still disagree with the files, and the generation config drops the base's end-of-turn stop token. 11 + 5 + 20 + 20 + 5 + 0 = 61.

LFM3-Audio-2B 52

Model card 17, Intended use (local agents, tool calling, structured outputs, fine-tuning), limitations (not recommended for agentic coding or complex multi-step reasoning, voice chat in English only), an architecture section, parameters (2B), context (32K) and 19 speech languages and locales. 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 31 October, edited the card. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (27 and 31 October 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. 17 + 5 + 20 + 0 + 5 + 5 = 52.