vllm-project/recipes
Grade a repo

52

/ 100

GradeF

Popular for its size, but the engineering basics lag behind the interest.

Higher than 37% of 5,156 graded repos

Common recipes to run vLLM

Documentation80
Engineering19
Health89
JavaScript884Apache-2.01mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (85).

See your top fixes
Now
F
52
Potential
B
85

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    Tests18pt

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  2. 2
    CI/CD14pt

    If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

  3. 3
    README12pt

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

  4. 4
    Install and run instructions9pt

    Add a section showing how to start or use the project.

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

80

Install and run instructions9pt45

README documents how to install the project.

README12pt90

README is present.

Contributing guide5pt92

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

19

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt70

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (devDependency in package.json).

Project health

89

Dependency manifest6pt65

Dependency manifest found (package.json).

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

  • 58 / 197
    Commits (30d / 90d)
  • 315
    Forks
  • 0
    Releases

Community

  • 62% - Fair
    Community health
  • 6 bus factor
    authors own >50% of commits
  • 884
    Watchers

Responsiveness

  • 1h
    Median issue response
  • 2h
    Median PR merge time
  • 116
    Open issues
Repository files48 root entries
  • .claude
  • ArceeAI
  • DeepSeek
  • Ernie
  • GLM
  • Google
  • inclusionAI
  • InternLM
  • InternVL
  • Jina
  • LiquidAI
  • Llama
  • Meituan
  • Microsoft
  • MiMo
  • MiniMax
  • Mistral
  • models
  • moonshotai
  • NVIDIA
  • OpenAI
  • overrides
  • PaddlePaddle
  • public
  • Qwen
  • scripts
  • Seed
  • src
  • StabilityAI
  • StepFun
  • strategies
  • Tencent-Hunyuan
  • Wan-AI
  • .gitignore
    Good: .gitignore present.
  • .readthedocs.yaml
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • jsconfig.json
  • LICENSE
    Good: Licensed under Apache-2.0.
  • mkdocs.yml
  • next.config.mjs
  • package.json
    Good: Dependency manifest found (package.json).
  • platforms.yaml
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • postcss.config.mjs
  • 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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • requirements.txt
  • taxonomy.yaml
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/recipes)](https://www.repo-grade.com/report/vllm-project/recipes)

More graded JavaScript repos