Modelverse separates canonical model facts, immutable versions, measured Runs, verification evidence and legal metadata so users can see what supports each recommendation.
A Run records the exact model revision, runtime version, hardware, configuration, task, evaluation method, metrics and evidence artifacts. Published Runs are effectively immutable. A correction creates a new revision and preserves the prior record.
A versioned JSON manifest can move between the CLI, API, evaluation frameworks and third-party tools.
Every metric links back to the conditions that produced it.
Builders can fork an existing recipe and publish the result on equivalent or different hardware.
A builder manually entered the result. Useful as an early claim, but not treated as verified.
Logs, outputs, source code or a machine-readable result are linked.
The Modelverse CLI captured hardware, versions and metrics and applied privacy redaction.
A different account reproduced the result and linked a new Run.
The Run used a published suite, fixed revision and approved runner.
An evidence-backed Run exists on equivalent hardware within the selected memory constraint.
The model’s quantized weight estimate and runtime overhead leave a safety margin, but no direct Run exists.
There is insufficient evidence, or the estimated working set exceeds the selected constraint.
The starter uses transparent rules in TypeScript and SQL. It does not use an opaque recommendation model. Estimated fit is never displayed as verified.
“Open” is not stored as one Boolean. The platform records weight availability, source code, training code, data information, commercial use, redistribution, derivative rights and use restrictions separately. SPDX identifiers are used where possible, and a visible classification is derived from those facts.
Meets the project’s strictest openness criteria with supporting evidence.
Weights are available, but one or more preferred forms for modification may be incomplete.
Access exists, but intended use is materially restricted.
The source contains custom, missing or contradictory terms requiring review.
Modelverse license labels are informational metadata, not individualized legal advice.
The initial search score combines text relevance, exact task match, runtime support, hardware compatibility, evidence level, maintainer claim status and recent verified activity. Spam and dispute flags subtract from the score. Each recommendation should be able to explain its major inputs.
text relevance + exact task match + runtime compatibility + confirmed hardware evidence + verification level + maintainer claim + recent relevant activity - spam and dispute penalties
The CLI redacts common tokens, secret keys, home-directory paths and personal machine identifiers before publishing. Users preview what will be uploaded. The web application does not execute arbitrary model repository code. Hosted evaluations require a separate isolated job control plane with disposable environments, network controls and resource limits.
