vllm-project/vllm-ascend

0

/ 100

Documentation84
Engineering72
Health100
C++2,277Apache-2.01d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

Community maintained hardware plugin for vLLM on Ascend

Documentation

84

Contributing guide5pt52

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.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

72

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

CI/CD14pt68

CI is configured (.github/workflows/_e2e_nightly_multi_node.yaml).

Tests18pt80

Test files detected (.github/workflows/scripts/conftest.py).

Reproducibility6pt92

Lockfile present (requirements.txt). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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)
  • 1,433
    Forks
  • 37
    Releaseslatest 1y ago

Community

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

Responsiveness

  • <1h
    Median issue response
  • 6h
    Median PR merge time
  • 2,094
    Open issues
Repository files46 root entries
  • .agents
  • .claude
  • .gemini
  • .github
    Good: Test files detected (.github/workflows/scripts/conftest.py).
    Good: CI is configured (.github/workflows/_e2e_nightly_multi_node.yaml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • benchmarks
  • cmake
  • csrc
  • docs
  • examples
  • tests
  • tools
  • vllm_ascend
  • .clang-format
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .markdownlint.yaml
  • .pre-commit-config.yaml
  • .readthedocs.yaml
  • AGENTS.md
  • CLAUDE.md
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • collect_env.py
  • CONTRIBUTING.md
    Issue: 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
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.310p
  • Dockerfile.310p.openEuler
  • Dockerfile.a3
  • Dockerfile.a3.openEuler
  • Dockerfile.a5
  • Dockerfile.a5.openEuler
  • Dockerfile.openEuler
  • format.sh
  • LICENSE
    Good: Licensed under Apache-2.0.
  • mypy.ini
  • packages.txt
  • 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.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README.zh.md
  • requirements-dev.txt
  • requirements-lint.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • setup.py
  • typos.toml