SmolLM3-3B vs Step 3.7 Flash

SmolLM3-3B 74

Model card 14, it covers limitations, architecture, parameters, context and languages but has no intended-use section and leaves the June 2025 cut-off to the chat template. Training data 20, the datasets, mixture weights and post-training set are published with sources and sizes. Last change 20, Hugging Face's ONNX build changed its tokenizer config on 28 October 2026, though the main repository hasn't changed since 10 September 2025. Responsiveness 10, staff answered 14 of 36 discussions, none since November 2025. Version policy 5, a first release never replaced, with no dated notes. File health 5, template and tokenizer reports wait with no reply.

Step 3.7 Flash 39

Model card 14, Intended use, the architecture, the parameters, the context and the language (in the metadata) are on the card. Training data 0, Nothing on the card about the training data. Last change 10, the last commit, on 3 June 2026, fixed the modelling code, 160 days before this check and within 180. Responsiveness 0, none of the 11 most recent discussions that aren't pull requests (29 May to 24 June 2026) has a reply from a stepfun-ai member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, Step-3.5-Flash stays in its own repositories and 3.7 came out in new ones, with no dated note on the older cards that we read. File health 10, Config, template and card agree on the architecture and the context, and June commits fixed the modelling code. 14 + 0 + 10 + 0 + 5 + 10 = 39.

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.

Step 3.7 Flash 45

File safety 15, safetensors and GGUF only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the stepfun-ai organisation, which the card's StepFun platform and model page belong to (10). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations section and gives no guidance on prompt injection, instruction priority, refusals or safeguards. Licence risk 15, Apache 2.0 has no use policy, threshold or change clause. Security programme 0, no way to report a flaw on the card, and our StepFun API listing found no security.txt, bug bounty or disclosure policy. 15 + 15 + 0 + 0 + 15 + 0 = 45.

SmolLM3-3B 85

Memory 30, the smallest 4-bit build Hugging Face publishes is its own ONNX q4f16 at 2.1 GB, about 2.5 GB with the fifth added, and the full BF16 files that the counted runtimes load come to about 7.4 GB, both under 16 GB. Runtimes 20, released Transformers carries the model code, llama.cpp knows the architecture, and vLLM and SGLang run it through their Transformers backends in released versions; Ollama has no library entry and LM Studio's catalogue has none, so those two earn nothing. Builds 10, Hugging Face's ONNX repository has 4-bit builds, one of the checklist's kinds, and int8 builds, which are neither FP8 nor GGUF. They run in ONNX Runtime and Transformers.js rather than the runtimes above. Terms 15, plain Apache 2.0, scored by its terms since the repository holds no LICENSE file. Download 10, not gated. Hosted 0, no inference provider is listed for it on the Hub and none of the provider lists checked carries it.

Step 3.7 Flash 70

Memory 5, the smallest build at 4 bits is StepFun's IQ4_XS GGUF, 104.99 GB with the 3.97 GB projector, and 108.96 GB × 1.2 = 130.8 GB, over what the reference machine can give a model and within 256 GB. The IQ3 and Q3 builds are below 4 bits and aren't read. Runtimes 20, Released vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 have the step3p7 model, and llama.cpp b12242 has the architecture, with StepFun's own GGUF. Four at 5 each, and the card documents all four. Builds 15, StepFun publishes GGUF at five quantised precisions, an FP8 build and an NVFP4 build. Terms 15, Apache 2.0 in the card's metadata and its licence section, an OSI licence with nothing added. Download 10, the Hub API reports gated false for all four repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, StepFun's own API serves it, per the card and our StepFun API listing, and Featherless and DeepInfra are live for it on Hugging Face. 5 + 20 + 15 + 15 + 10 + 5 = 70.

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.

Step 3.7 Flash 85

Chat template 20, chat_template.jinja in the repository (5,723 characters). Tool-calling format 25, the card names the parser to use in two runtimes, step3p5 in vLLM (with auto tool choice) and in SGLang, and both ship Step parsers in a release. Trained tool calling 20, the card presents tool orchestration as a main use, with multi-turn results, and the template renders every call in a turn. Structured output 0, Nothing on the card about JSON or schema-constrained output for the weights. Reasoning control 10, the template has a reasoning_effort setting and keeps reasoning_content, and the card names the step3p5 reasoning parser for vLLM and SGLang, which returns the reasoning apart from the answer. Context 10, 256K tokens per the card, and 262,144 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.