vLLM has an HVTrust score of 81.5/100 (Grade A), ranked #65 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for vLLM?

vLLM scores 81.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 88.6k GitHub stars and is categorized under LLM Gateways & Infra.

vLLM

vllm-project/vllm

A high-throughput and memory-efficient inference and serving engine for LLMs

LLM Gateways & Infra Python Grade A Listed Apache-2.0

81.5/100

Rank #65 of 1204

Compare vLLM

How does it stack up against its LLM Gateways & Infra neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Tool Surface Changed +1

Is vLLM safe? vLLM scores 81.5/100 (Grade A), ranked #65 of 1204 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.6/10; 100% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in LLM Gateways & Infra

#1 Bifrost — 88.3 (A) → #2 Headroom — 86.7 (A) → #4 LiteLLM — 75.7 (B) → #5 Ollama — 67.7 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, OpenAI, Postgres

2026-07-21

Grade Changed

Trust grade A → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.6/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with Bifrost Get email alerts for vLLM View LLM Gateways & Infra Report missing data

99.7

Activity sub-score · out of 100

In LLM Gateways & Infra

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

88.6k

Forks

20.5k

Last Push

2026-08-09

today

Commits (4 wk)

1094

Downloads (7d)

1,159,177

pypi

HN mentions (30d)

1001

Open Issues

2099

Rank Change

▼3

was #62

Analysis

HVTrust Dimensions vs LLM Gateways & Infra

81.5 / 100 · 100.0% confidence

vLLM LLM Gateways & Infra average (13 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

13.2 / 25

3.1 above avg 10.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.1 below avg 11.9

Transparency50% declared license · 50% OSSF Scorecard

14.1 / 17

2.0 above avg 12.1

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

2.7 above avg 17.3

AdoptionLog-scaled stars · package downloads

20.0 / 20

6.1 above avg 13.9

Activity Inputs

99.7 / 100

StarsRepository reach

29.7 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

20 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.6 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 5

Code-Review 9

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 1

Security-Policy 10

Signed-Releases 0

Token-Permissions 9

Vulnerabilities 0

Is vLLM safe?

Public supply-chain signals for vLLM are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but vLLM carries less obvious unverified-evidence risk than projects with thin signals.

Does vLLM publish package provenance?

No published build provenance is currently detected for vLLM. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does vLLM have an OpenSSF Scorecard?

vLLM has an OpenSSF Scorecard score of 6.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is vLLM actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does vLLM use?

vLLM ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are vLLM's commits signed?

100% of the last 100 commits to vLLM are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare vLLM head-to-head

vLLM vs Bifrost → vLLM vs Headroom → vLLM vs LiteLLM →

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to vLLM's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, OpenAI, Postgres

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI, Postgres

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain vLLM?

For maintainers

HVTrust scores vLLM from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, OpenAI, Postgres

2026-07-21

Grade Changed

Trust grade A → B

2026-07-19

Grade Changed

Trust grade B → A

2026-07-13

Grade Changed

Trust grade A → B

2026-07-11

Grade Changed

Trust grade B → A

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI, Postgres

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-06-03

Scorecard Added

OSSF Scorecard: 6.6/10

2026-06-03

Grade Changed

Trust grade D → B

2026-06-03

Rank Moved

Rank rose 107 spots (#139 → #32)

2026-06-03

HVTrust Changed

HVTrust up 29.9pts (48.1 → 78.0)

2026-06-02

Newly Listed

First tracked at rank #139

GitHub → PyPI: vllm

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/vllm.svg)](https://hvtracker.net/agents/vllm)
            
HTML:
            <a href="https://hvtracker.net/agents/vllm"><img src="https://hvtracker.net/badge/vllm.svg" alt="HVTrust"></a>

Other agents in LLM Gateways & Infra

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON