88
/ 100
Excellent work. The main thing left to polish is CI.
V100 / SM70-focused vLLM engineering fork for modern LLM inference.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
86
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
92
CI is configured (.github/workflows/macos-smoke-test.yml).
Test files detected (.buildkite/lm-eval-harness/conftest.py).
Linter or formatter configured (rust/rustfmt.toml).
Lockfile present (benchmarks/kernels/requirements.txt). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 224 / 3939Commits (30d / 90d)
- 277Forks
- 10Releaseslatest 1mo ago
Community
- 100% - GoodCommunity health
- 4 bus factorauthors own >50% of commits
- 1,450Watchers
Responsiveness
- 1d 4hMedian issue response
- -Median PR merge time
- 205Open issues
Repository files49 root entries
- .buildkiteGood: Test files detected (.buildkite/lm-eval-harness/conftest.py).
- .gemini
- .githubGood: CI is configured (.github/workflows/macos-smoke-test.yml).Good: Dependabot covers 2 ecosystems (github-actions, pip). Dependencies stay current.Good: Issue or PR templates present.
- assets
- benchmarksGood: Lockfile present (benchmarks/kernels/requirements.txt). Installs are reproducible.
- cmake
- csrc
- dockerGood: Environment pinned via docker/Dockerfile.
- docs
- examples
- flash_qla
- flash-attention-v100
- flashinfer-sm70
- requirements
- rustGood: Linter or formatter configured (rust/rustfmt.toml).
- scripts
- tests
- tools
- vllm
- .clang-format
- .coveragerc
- .dockerignore
- .git-blame-ignore-revs
- .gitignoreGood: .gitignore present.
- .markdownlint.yaml
- .pre-commit-config.yaml
- .readthedocs.yaml
- .shellcheckrc
- .yapfignore
- AGENTS.md
- build_rust.sh
- CLAUDE.md
- CMakeLists.txt
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- codecov.yml
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.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).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- DCO
- LICENSEGood: Licensed under Apache-2.0.
- MANIFEST.in
- mkdocs.yaml
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: 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.
- RELEASE.md
- rust-toolchain.toml
- SECURITY.mdGood: Security policy present.
- setup.py
- SM70_FLASH_V100_QUALITY_EXPERIMENT_LOG_20260615.md
- SM70_MTP_OUTPUT_QUALITY_AUDIT_20260616.md
- use_existing_torch.py
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/1catai/1cat-vllm)