rocm/transformerengine

0

/ 100

Documentation68
Engineering72
Health72
Python70Other1d ago
Grade a repo

Solid foundation. Invest in docs and CI to grow from here.

Documentation

68

README12pt40

README is present.

Contributing guide5pt59

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

72

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.

CI/CD14pt72

CI is configured (.github/workflows/build.yml).

Tests18pt80

Test files detected (examples/jax/collective_gemm/conftest.py).

Reproducibility6pt80

Lockfile present (benchmarks/attention/requirements.txt). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

72

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Dependency manifest6pt62

Dependency manifest found (pyproject.toml).

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)
  • 34
    Forks
  • 11
    Releaseslatest 3mo ago

Community

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

Responsiveness

  • 1d 7h
    Median issue response
  • 6d 2h
    Median PR merge time
  • 60
    Open issues
Repository files26 root entries
  • .claude
  • .github
    Good: Licensed under Other.
    Good: CI is configured (.github/workflows/build.yml).
    Good: Environment pinned via .github/actions/build-pytorch-wheel/Dockerfile.
    Good: Issue or PR templates present.
  • 3rdparty
  • benchmarks
    Good: Lockfile present (benchmarks/attention/requirements.txt). Installs are reproducible.
  • build_tools
  • ci
  • docs
  • examples
    Good: Test files detected (examples/jax/collective_gemm/conftest.py).
  • qa
  • tests
  • transformer_engine
  • .clang-format
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .pre-commit-config.yaml
  • Acknowledgements.txt
  • CLAUDE.md
  • CONTRIBUTING.rst
    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).
    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.
  • CPPLINT.cfg
  • LICENSE
  • MANIFEST.in
  • pylintrc
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.rst
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
    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.
  • SECURITY.md
    Good: Security policy present.
  • setup.py