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

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

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

  • Commits (30d / 90d)
  • 423
    Forks
  • 22
    Releaseslatest 1y ago

Community

  • Community health
  • authors own >50% of commits
  • 2,421
    Watchers

Responsiveness

  • 3h
    Median issue response
  • 1h
    Median PR merge time
  • 165
    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.