Is vLLM safe?
vLLM scores 80.0/100 (Grade A), ranked #56 of 418 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.8/10;
100% of recent commits are signed;
last pushed 2026-07-19. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Strong public trust posture, backed by multiple independent signals.
80.0/100 · Grade A
Strongest Signal
Maintenance
20.0/20
Weakest Signal
Safety / Integrity
13.5/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 6.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
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 →
Signals refreshed2026-07-19 08:02 UTC·Repo last pushed today
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.8/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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
database
search
shell
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.
Detected MCP server support changed: none → declared
Maintain vLLM?
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.
