albert-base-v2
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
CONFLICT INTELLIGENCE · SOURCE VS SOURCE
When sources differ, classify the difference before calling it a conflict.
Open Model Weights separates explicit contradictions from scope, granularity and claim-strength differences. Missing evidence never becomes agreement, falsehood or conflict.
0 active conflicts115 comparison signals713/713 current claim-schema coverageMissing stays unknown
ACTIVE SOURCE CONTRADICTIONS
Comparable claims that do not match.
A conflict requires comparable field, scope and claim strength. Parameter naming, component scope and generic license metadata do not automatically qualify.
NO ACTIVE CONFLICTS IN CHECKED COMPARABLE FIELDS
No current source contradiction is retained.
This does not mean every source agrees. It means no contradiction is detected within the currently comparable checked fields; incomplete claim coverage and comparison signals remain explicit.
COMPARISON SIGNALS · NOT CONFLICTS
Differences worth seeing without overstating them.
These values differ, but current evidence does not establish that they describe the same quantity, scope or legal classification. OMW keeps them visible and separate.
gte-reranker-modernbert-base
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
OpenELM-1_1B-Instruct
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
ESMC-6B
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
CodeLlama-7b-hf
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
DeepSeek-Coder-V2-Lite-Instruct
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
DeepSeek-V3
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
DeepSeek-V4.1-Flash
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
DeepSeek-V4-Flash
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
DeepSeek-V4-Flash-DSpark
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Devstral-2-123B-Instruct-2512
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
distilbert-base-multilingual-cased
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
distilroberta-base
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
dots.ocr
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
pythia-160m
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
pythia-6.9b
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
pythia-70m
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
pythia-70m-deduped
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
cryptobert
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Bio_ClinicalBERT
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
dinov3-vitl16-pretrain-lvd1689m
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
OTel-2.0-LLM-31B-IT
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
gliner2-base-v1
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
embeddinggemma-300m
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
SmolLM2-135M
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
SmolLM2-135M-Instruct
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
SmolLM3-3B
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
SmolVLM-256M-Instruct
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
granite-4.1-3b
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
granite-embedding-small-english-r2
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
granite-timeseries-tspulse-r1
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
K2-Horizon-375B-A23B
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
K2-Horizon-MoVA-36B-A4B
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
jina-embeddings-v3
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
jina-reranker-v3
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Llama-4-Maverick-17B-128E
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-4-Maverick-17B-128E-Instruct
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-4-Maverick-17B-128E-Instruct-FP8
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-4-Maverick-17B-128E-Instruct-FP8-Original
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-4-Maverick-17B-128E-Instruct-Original
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-4-Maverick-17B-128E-Original
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-4-Scout-17B-16E
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-4-Scout-17B-16E-Instruct
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-4-Scout-17B-16E-Instruct-Original
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-4-Scout-17B-16E-Original
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-Guard-4-12B
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-Prompt-Guard-2-22M
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-Prompt-Guard-2-22M
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Llama-Prompt-Guard-2-86M
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Llama-Prompt-Guard-2-86M
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Meta-Llama-3-70B-Instruct
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Meta-Llama-3-8B-Instruct
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Meta-Llama-3-8B
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Phi-3.5-mini-instruct
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Phi-3.5-vision-instruct
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Phi-3-mini-4k-instruct
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
phi-4
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Phi-4-mini-instruct
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Phi-4-mini-instruct
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
VibeVoice-1.5B
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
MiniMax-H3
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Mistral-Medium-3.5-128B
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Mistral-Medium-3.5-128B-EAGLE
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Kimi-K2.5
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Kimi-K2.5
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Kimi-K2.6
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Kimi-K2-Instruct
license · classification granularity
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Kimi-K2-Instruct
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
nomic-embed-text-v2-moe
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
llama-nemotron-rerank-1b-v2
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
nemotron-3.5-asr-streaming-0.6b
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
NVIDIA Nemotron 3 Nano 30B-A3B
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Nemotron-3-Nano-Omni-30B-A3B-Reasoning-BF16
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Nemotron-3-Nano-Omni-30B-A3B-Reasoning-FP8
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Nemotron-3-Nano-Omni-30B-A3B-Reasoning-NVFP4
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
nemotron-speech-streaming-en-0.6b
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
NVIDIA-Nemotron-3.5-Lightning-30B-A3B-BF16
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
NVIDIA-Nemotron-3.5-Lightning-30B-A3B-BF16
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
NVIDIA-Nemotron-3.5-Lightning-30B-A3B-NVFP4
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
NVIDIA-Nemotron-3.5-Lightning-30B-A3B-NVFP4
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
NVIDIA-Nemotron-3-Nano-30B-A3B-NVFP4
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
NVIDIA-Nemotron-3-Super-120B-A12B-BF16
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
NVIDIA-Nemotron-3-Super-120B-A12B-BF16
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
NVIDIA-Nemotron-3-Super-120B-A12B-NVFP4
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
NVIDIA-Nemotron-3-Super-120B-A12B-NVFP4
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
NVIDIA-Nemotron-3-Ultra-550B-A55B-BF16
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
NVIDIA-Nemotron-3-Ultra-550B-A55B-BF16
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Octen-Embedding-8B
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
gpt2
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
gpt2-large
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
privacy-filter
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
MiniCPM-o-2_6
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
MiniCPM-o-4_5
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
VoxCPM2
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Ornith-1.5-35B-A3B
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Ornith-1.5-35B-A3B-NVFP4
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Qwen-Image-2.1
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Qwen-Image-2.1-PE-I2I
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Qwen-Image-2.1-PE-T2I
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Qwen2.5-VL-32B-Instruct
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Qwen2.5-VL-3B-Instruct
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Qwen2.5-VL-7B-Instruct
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Qwen3-30B-A3B-Instruct-2507
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Qwen3-Coder-Next
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
Qwen3-Coder-Next-FP8
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
snowflake-arctic-embed-l
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Apertus-v1.5-8B
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Hy3
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
falcon-7b
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
vitpose-plus-base
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
GLM-5
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
GLM-5.2
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
GLM-5.2-FP8
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
GLM-5.3-Flash
context tokens · context scope difference
Config and model-card context values differ, but the extracted model-card number is not scope-qualified. It may describe an evaluation, generation limit or deployment setting rather than the model capability. OMW therefore does not classify this as a contradiction.
GLM-OCR
total parameters billions · scope or granularity difference
Values differ, but current evidence does not establish that they measure the same scope or granularity. This is not classified as a conflict.
Comparable values only
Context is compared with context only after current claim parsing; parameter scope and component boundaries remain explicit.
Evidence before interpretation
Both source values and URLs remain attached. Classification is a separate OMW layer.
No absence inference
A missing model-card claim, license file or runtime document is incomplete evidence, not agreement and not a negative claim.
Detector corrections stay visible
When a detector refinement reclassifies an earlier alert, history records the correction rather than pretending it never happened.