meta-pytorch/torchcomms

0

/ 100

Documentation88
Engineering79
Health100
C++372BSD-3-Clause1d ago
Grade a repo

Polished and well engineered. Punching above its star count.

torchcomms: a modern PyTorch communications API

Documentation

88

Contributing guide5pt66

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt90

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under BSD-3-Clause.

Engineering

79

CI/CD14pt57

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

Tests18pt80

Test files detected (comms/common/algorithms/all_gather/tests).

Reproducibility6pt92

Lockfile present (comms/ncclx/v2_29/bindings/nccl4py/uv.lock). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (comms/rcclx/develop/projects/amdsmi/.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (comms/ncclx/v2_29/bindings/nccl4py/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)
  • 153
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 372
    Watchers

Responsiveness

  • 6d 21h
    Median issue response
  • —
    Median PR merge time
  • 558
    Open issues
Repository files17 root entries
  • .github
    Good: CI is configured (.github/workflows/build_test_rccl.yaml).
  • comms
    Good: Test files detected (comms/common/algorithms/all_gather/tests).
    Good: Linter or formatter configured (comms/rcclx/develop/projects/amdsmi/.editorconfig).
    Good: Lockfile present (comms/ncclx/v2_29/bindings/nccl4py/uv.lock). Installs are reproducible.
    Good: Environment pinned via comms/rcclx/develop/projects/amdsmi/Dockerfile.
    Good: Dependabot is configured. Dependencies update automatically.
    Good: Issue or PR templates present.
    Good: Security policy present.
    Good: Dependency manifest found (comms/ncclx/v2_29/bindings/nccl4py/pyproject.toml).
  • .clang-format
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .lintrunner.toml
  • .pyre_configuration
  • build_ncclx.sh
  • build_rccl.sh
  • build_rcclx.sh
  • CLAUDE.md
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • LICENSE
    Good: Licensed under BSD-3-Clause.
  • MANIFEST.in
  • 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.