Not every difference is a contradiction. Investigate model weights, context claims and license evidence with the original sources side by side.
The short answer: An active conflict requires two explicit, comparable claims that disagree. Less certain differences remain comparison signals—not manufactured conflicts.
A conflict is listed only after the compared source values have matching meaning and scope. The original claims remain visible.
No active comparable-source contradictions in this snapshot.
That does not imply complete agreement or universal coverage. Browse the source differences below and review what the current detector can compare.
03 / Derivative license provenance
Licenses carry a lineage.
Original model licenses and derivative declarations need their own evidence review. These candidates are not confirmed violations or active conflicts.
License provenance · review required
DeepSeek-R1-Distill-Llama-8B
Derivative declaration: MIT (publisher repository declaration) /Declared base: Meta Llama 3.1 8B (Llama 3.1 Community License)
The derivative publisher declares MIT for its checkpoint while also naming Llama 3.1 and its separate base-model terms. The original and downstream license conditions require component-aware review; this is not evidence of a legal violation.
Not a confirmed conflict or legal finding · omw:license-provenance:v1:deepseek-r1-distill-llama-8b
02 / Wider evidence landscape
Most differences need context.
The counts below are source comparison signals, not confirmed contradictions. Investigate by category, model, or value without losing the full audit trail.
Open any category to inspect source values and the classification rationale. Every record remains in the page and downloadable API.
152 source comparisons
152 comparison signals available. Choose a category to open its evidence.
Parameter counts87 source differences+
Total parameters and reported values need matching units, expert scope and precision. Every linked record below remains a comparison signal, not a confirmed contradiction.
A bare context number cannot be promoted to verified maximum supported context. Every linked record below remains a comparison signal, not a confirmed contradiction.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
A metadata mismatch is not automatically an incompatible license. Every linked record below remains a comparison signal, not a confirmed contradiction.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
License labels differ in specificity or classification granularity. The evidence does not establish contradictory legal terms, so this is not classified as a conflict.
Source integrity matters more than an alarming total. Our classifier publishes uncertainty rather than guessing what a publisher meant.
01
Compare like with like
A true contradiction requires matching field, units, scope, artifact and claim strength. An active-expert count need not match total model parameters.
02
Inspect both originals
Open the source links beside the values. Licensing metadata is not a substitute for legal terms, and an unqualified context number is not a tested runtime limit.
03
Retain uncertainty
Missing claims remain unknown. Historical detector corrections, first-observed dates and stable evidence IDs preserve how conclusions were reached.
A confirmed disagreement between explicit values that are comparable in field, scope and claim strength. One source being silent is not an active conflict.
Why are there more comparison signals than active conflicts?
A difference between repository metadata, model cards or config files can reflect rounding, scope, naming or a weaker statement. Those signals are published for investigation without labeling them contradictions.
How current is this page?
The evidence snapshot date shows when the retained source-comparison dataset was generated. Each record includes original source links and observation history. The page is not a live real-time scan of every upstream repository.
Can I treat a license comparison as legal advice?
No. Read the exact repository license file and governing terms for the checkpoint. Automatic license classification is supporting evidence, not legal permission.