gpt-oss-20b vs Granite 4.2 8B

gpt-oss-20b 42

The model card earns 17, covering six of the seven points and missing a statement of supported languages. Training data earns 10, a general description with a June 2024 cut-off and no sources or mix. Last change earns 5, because the files haven't changed since August 2025 and the reference code and harmony parser last changed on 1 and 5 November 2025, still within a year on 1 November 2026, while this year's commits only touch the browser tool, CI and a version number. Responsiveness earns 0, with no OpenAI reply to any of the 40 most recent discussions and none at all since August 2025. Version policy earns 5 for a first release kept in its own repository. File health earns 5, since template reports and an install report wait without a reply.

Granite 4.2 8B 92

Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (8B), context length (128K native) and 12 tested languages are on the card. Training data 20, IBM's disclosure file for the 8B lists the datasets used in pre-training and post-training as machine-readable metadata, and the card describes the three training stages. Last change 20, the last commit, on 20 October 2026, replaced model.safetensors.index.json (titled "granite-4.2 index file fix"), 21 days before this check. Responsiveness 20, Of the 5 discussions that aren't pull requests (13 September to 5 November 2026), 4 have a reply from an ibm-granite member. Version policy 5, Granite 4.1 8B stays in its own repository and 4.2 came out in new ones. File health 10, Config, template and card agree on the architecture, the 131,072-token context and the thinking switch. 17 + 20 + 20 + 20 + 5 + 10 = 92.

gpt-oss-20b 85

File safety earns 25, since the weights are safetensors and metal/model.bin is OpenAI's own raw Metal format rather than pickle, and nothing in the repository runs as code (a judgement call on the .bin name). Provenance earns 15, files in OpenAI's own organisation and a checksum on every file. Safety evaluation earns 10, because the published safety results for this size are OpenAI's own, and the outside review covered gpt-oss-120b. Agent guidance earns 15 for an instruction hierarchy the model was trained to follow, with prompt-injection results, though OpenAI reports it trails o4-mini there. Licence risk keeps 15, with nothing to deduct under Apache 2.0. The security programme earns 5 for OpenAI's security.txt with a Bugcrowd contact. Public advisories for the gpt-oss code couldn't be checked, so that half scores as absent.

Granite 4.2 8B 55

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the ibm-granite organisation, which IBM's Granite docs and the GitHub README link to (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, and the card's licence link resolves. Security programme 5, www.ibm.com/.well-known/security.txt names IBM PSIRT, read for the 3B listing on 4 November 2026 (5). 15 + 15 + 0 + 5 + 15 + 5 = 55.

gpt-oss-20b 90

Memory earns 25, since OpenAI's own MXFP4 build is 13.76 GB and a fifth on top is 16.5 GB, just past the 16 GB band, and Ollama's 14 GB build lands in the same 24 GB band. Runtimes earn the full 25 from model code in released Transformers, vLLM and SGLang, the architecture in llama.cpp and the model in Ollama's library. Builds earn 10, because OpenAI ships one quantised precision, MXFP4, and the original and metal folders are the same weights for its reference code. Terms earn 15 for Apache 2.0, whose usage policy only asks users to follow the law. Download earns 10, since the repository isn't gated. Hosted earns 5, with five inference providers live for it on its Hugging Face page on 1 November 2026, while OpenAI's own API lists it with no usable rate limit and isn't counted.

Granite 4.2 8B 95

Memory 30, IBM's own 4-bit MLX build granite-4.2-8b-q4-mlx is 4.95 GB, and 4.95 GB × 1.2 = 5.9 GB, within 8 GB. Its Q4_0 GGUF is 5.06 GB and Ollama's library build granite4.2:8b (5.3 GB) fits 8 GB too. Runtimes 25, Released versions run the granite architecture in llama.cpp (granite, b12242), vLLM (GraniteForCausalLM in the v0.33.0 registry), SGLang (granite.py at v0.5.23), Transformers (v5.22.2) and Ollama (its own granite4.2 library entry, 8b tag). Builds 15, IBM publishes FP8, MXFP4 and NVFP4 safetensors builds, a GGUF repository with Q4_0 to Q8_0 and BF16 files, and 4-bit, 8-bit and BF16 MLX builds, so quantised builds at two precisions or more. Terms 15, Apache 2.0, an OSI-approved licence, with no use policy or other terms added on the card. Download 10, the Hub API reports gated false for the BF16, FP8, MXFP4, NVFP4, GGUF and MLX repositories, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps one inference provider (DeepInfra, live), short of the two the line needs. 30 + 25 + 15 + 15 + 10 + 0 = 95.

gpt-oss-20b 90

The chat template earns 20, a Jinja file in the repository. The tool-calling format earns 25, since OpenAI's harmony guide says how functions are declared and how calls come back, and OpenAI ships the openai-harmony parser. Trained tool calling earns 10, because each call ends the message and waits for its result, so it makes one call at a time. Structured output earns 15 for a JSON Schema given in the developer message, documented in the harmony guide. Reasoning control earns 10, with low, medium or high effort per request and the reasoning on its own channel, though it can't be switched off. Context earns 10 for 131,072 tokens, which OpenAI describes as trained in even though the config reaches it with YaRN.

Granite 4.2 8B 85

Chat template 20, chat_template.jinja in the repository, with roles, tools, tool responses, the thinking switch and low effort. Tool-calling format 25, the card has tool-calling sections for vLLM and SGLang, declares tools with OpenAI's function schema and names the parser to use, qwen3_coder, which both runtimes ship in the released versions read. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so it renders several calls in one turn, and the card names tool calling and agentic workflows as what it's best for. Structured output 0, the card doesn't document JSON or JSON Schema output or how to ask for it. Reasoning control 10, the card documents thinking on by default, non-thinking and low-effort modes per request through the template (enable_thinking and low_effort), with the reasoning returned apart from the answer. Context 10, 131,072 tokens natively per the card and config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.