Item detail
github.com

vllm-project/vllm

RepoRadar surfaced vllm-project/vllm — an AI project — into the LLM Inference section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is practical usefulness, scored 10.0 out of 10.

Score9.8
Popularity99.0
Riskconditional
TierGold
Score breakdown
Usefulness10.0
Novelty9.0
Momentum10.0
Maturity9.5
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease4.2

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Use this if you run LLM APIs today and care about throughput, latency, and memory efficiency.

Who should use it

ML platform teams startups exposing internal APIs for LLM apps MLOps teams optimizing throughput and GPU utilization

Who should skip it

Consider vllm-project/vllm lower priority if you already have a working solution in this category.

About this signal

vllm-project/vllm is tracked by RepoRadar as an AI project in the LLM Inference section. It was first seen on 2026-06-18 and last updated on 2026-06-18. The current verdict is 'try now' with a Gold tier and advanced setup difficulty. The standout signals for vllm-project/vllm are practical usefulness (10.0) and momentum (10.0), while setup ease (4.2) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned vllm-project/vllm a composite score of 9.8 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 99.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

GPU-heavy deployments require careful capacity planning and model compatibility checks; Serving misconfiguration can expose sensitive payloads or cause service instability under traffic spikes.

Evidence links
Closest alternatives / related signals
llm serving inference gpu performance
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-03T18:56:10Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

37 dated snapshots retained from 2026-06-18 through 2026-08-03; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score9.8 current · +0.0 net
Repository momentum10.0 current · +0.0 net
GitHub stars (observed)88,046 current · +1,915 net
GitHub stars88,046 exact observation
Versionv0.26.0
Last release2026-07-27T01:06:58Z
Maintenanceactive
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineOpenAI

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-039.810.088,046conditionaltry nowactive
2026-08-029.89.687,922conditionaltry nowactive
2026-08-019.89.087,838conditionaltry nowactive
2026-07-319.810.0Not recordedconditionaltry nownot recorded
2026-07-309.810.0Not recordedconditionaltry nownot recorded
2026-07-299.810.087,552conditionaltry nowactive
2026-07-289.89.087,423conditionaltry nowactive
2026-07-219.89.086,502conditionaltry nowactive
2026-07-209.89.086,502conditionaltry nowactive
2026-07-199.89.086,502conditionaltry nowactive
2026-07-189.89.086,502conditionaltry nowactive
2026-07-179.89.086,502conditionaltry nowactive

Why the record changed

stars changed

Stars changed: 87922 → 88046.

stars changed

Stars changed: 87838 → 87922.

stars changed

Source-observed stars changed: 87816 → 87838. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 87815 → 87816. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 87423 → 87552.

stars changed

Source-observed stars changed: 87406 → 87423. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 86502 → 87406.

version changed

Version changed: v0.25.1 → v0.26.0.

stars changed

Source-observed stars changed: 86499 → 86502. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 86498 → 86499. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 86497 → 86498. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 86493 → 86497. This reports the retained observation delta and does not infer why the upstream change occurred.