vllm-project/production-stack
Grade a repo

91

/ 100

GradeA

A well-known project done right. Strong docs and solid engineering throughout.

Top 11% of 5,156 graded repos

vLLM’s reference system for K8S-native cluster-wide deployment with community-driven performance optimization

Documentation90
Engineering89
Health98
Python2,435Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

8 to address
  1. 1
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  2. 2
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Reproducibility6pt

    Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.

  4. 4
    Dependency manifest6pt

    Add `authors = [...]` under [project] so the package has clear ownership.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

90

Contributing guide5pt77

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

89

Linting and formatting5pt0

No linter or formatter configured.

→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.

Reproducibility6pt92

Lockfile present (uv.lock). Installs are reproducible.

Tests18pt100

Test files detected (helm/tests).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

98

Dependency manifest6pt93

Dependency manifest found (pyproject.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 16 / 41
    Commits (30d / 90d)
  • 426
    Forks
  • 22
    Releaseslatest 1y ago

Community

  • 87% - Good
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 2,435
    Watchers

Responsiveness

  • 3h
    Median issue response
  • 1h
    Median PR merge time
  • 169
    Open issues
Repository files31 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • benchmarks
  • community
  • deployment_on_cloud
  • docker
    Good: Environment pinned via docker/Dockerfile.
  • docs
  • examples
  • helm
    Good: Test files detected (helm/tests).
  • observability
  • operator
  • proposals
  • scripts
  • src
  • tests
  • tutorials
  • utils
  • .codespell-ignore
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .hadolint.yaml
  • .markdownlint.yaml
  • .pre-commit-config.yaml
  • .readthedocs.yaml
  • artifacthub-repo.yml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements-test.txt
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/vllm-project/production-stack)](https://www.repo-grade.com/report/vllm-project/production-stack)

More graded Python repos