Nanbeige4.2-3B vs Swift 1.5 Qwen3.8-Flash-Next

Nanbeige4.2-3B 72

Model card 17, Intended use, limitations, the architecture, the parameters (3B outside the embeddings), the context and the languages (in the metadata) are on the card. Training data 5, A general description of how the fine-tuning and reinforcement learning data was built and filtered, with no sources, sizes or cut-off. Last change 15, the last commit, on 11 September 2026, updated modeling_nanbeige.py, 60 days before this check and within 90. Responsiveness 20, Of the 34 most recent discussions that aren't pull requests (21 July to 10 September 2026), 20 have a reply from a Nanbeige member, which is most. Version policy 5, Nanbeige's earlier models (Nanbeige4-3B, 4.1-3B) stay in their own repositories, as the Base, FP8, 8-bit and DSpark builds of this one do. File health 10, Config, tokenizer config, template and card agree on the architecture and the 262,144 tokens. 17 + 5 + 15 + 20 + 5 + 10 = 72.

Swift 1.5 Qwen3.8-Flash-Next 40

Model card 5 of 20, intended use and context only. Training data 5, a general description with no cut-off. Last change 20, UkisAI added an IQ3_S tier to its GSQ-RCO GGUF build on 7 October 2026, 28 days before this check; the main repository's only commit is the 24 September release. Responsiveness 0, UkisAI answered none of 3 discussions. Version policy 5, a first release, renamed without a note. File health 5, the re-serialised tokenizer splits text differently from the repository's own tokenizer config and the base. 5 + 5 + 20 + 0 + 5 + 5 = 40.

Nanbeige4.2-3B 85

Chat template 20, A Jinja chat template in tokenizer_config.json (7,961 characters), with enable_thinking, preserve_thinking, tools and tool_call_format switches. Tool-calling format 25, the card says passing tools switches on the tool template and recommends tool_call_format xml, with json for compatibility, and its SGLang and vLLM commands name the nanbeige tool-call parser, which released SGLang 0.5.23 has. Trained tool calling 20, the card describes fine-tuning on tool-use environments and agent scaffolds and reinforcement learning on agent tasks, and the template tells the model it may call one or more functions and renders every call in a turn. Structured output 0, Neither the card nor the files mention JSON or JSON Schema output, beyond json as a tool-call format. Reasoning control 10, the card documents enable_thinking, on by default and False per request, and preserve_thinking for earlier turns, and names the nanbeige reasoning parser, which returns the reasoning apart from the answer. Context 10, 262,144 tokens, which the card says the model supports and config.json gives as max_position_embeddings. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Swift 1.5 Qwen3.8-Flash-Next 60

Chat template 20, the base's Jinja file. Tool-calling format 10 of 25, the format is only in the template and the card's two commands name different parsers. Trained tool calling 20, several calls a turn and agentic post-training. Structured output 0, not documented. Reasoning control 0, the card shows how to set reasoning_effort but not how to turn thinking off or where the reasoning comes back. Context 10, 262,144 tokens native.

Nanbeige4.2-3B 85

Memory 30, the smallest build from Nanbeige is the FP8 repository (the 8-bit GPTQ one is the same size), 5.19 GB, and 5.19 GB × 1.2 = 6.2 GB, within 16 GB. bartowski's GGUF isn't read for this line. Runtimes 15, Released SGLang 0.5.23 has the model (srt/models/nanbeige.py) with its parsers, llama.cpp b12242 has the nanbeige architecture, and vLLM 0.33.0 names NanbeigeForCausalLM in its registry, served through its Transformers backend. Builds 15, Quantised builds from Nanbeige at two precisions, FP8 and 8-bit GPTQ, each in its own repository. Terms 15, Apache 2.0 in the card's metadata, an OSI licence, with no use policy or other terms on the card. Download 10, the Hub API reports gated false for the model and its FP8 and 8-bit 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, and no Nanbeige or BOSS Zhipin API for it was found. 30 + 15 + 15 + 15 + 10 + 0 = 85.

Swift 1.5 Qwen3.8-Flash-Next 65

Memory 5 of 30, the smallest 4-bit build is UkisAI's IQ4_XS GGUF at 98.6 GB with the vision projector, 118.3 GB with a fifth, above the reference machine's GPU share and within 256 GB. Runtimes 25, the architecture is Qwen3.8-Flash-Next's (qwen4_exp), which released llama.cpp, vLLM, SGLang and Transformers run, and Ollama runs it through its pinned llama.cpp (b11963 in v0.40.14), this run's reading for Ollama. Builds 15, GGUF, INT4 and NVFP4 builds from UkisAI. Terms 10, two custom licences that allow commercial use within limits. Download 10, not gated. Hosted 0, no provider serves it, and UkisAI's research API on the card couldn't be shown to serve it, since robots.txt disallows calling it. 5 + 25 + 15 + 10 + 10 + 0 = 65.

Nanbeige4.2-3B 55

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the Nanbeige organisation (Nanbeige LLM Lab), which the lab's arXiv report for this model links, so the publisher's own account, although the Hub hasn't verified it (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions: the limitations section says outputs may be inaccurate, biased or harmful. Licence risk 15, Apache 2.0 has no use policy, no threshold and no clause letting the licensor change or revoke it. Security programme 5, BOSS Zhipin runs a security response centre for reporting flaws in its products, as read for the Nanbeige4.3-33B listing (5), though nothing links it to the model. 15 + 15 + 0 + 5 + 15 + 5 = 55.

Swift 1.5 Qwen3.8-Flash-Next 45

File safety 25, safetensors only and no code in the repository, though the card's vLLM command passes trust-remote-code. Provenance 15, the files are in the account UkisAI's site links to, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 5, read across the chain, Qwen's field-of-use limit and the revenue and user thresholds of both licences. Security programme 0, no way to report a flaw was found.