cmcgirr-amd/torch-mlir

0

/ 100

Documentation82
Engineering55
Health64
0Other3y ago
Grade a repo

Rough and inactive. Tests, CI, and a fuller README would revive it.

The Torch-MLIR project aims to provide first class support from the PyTorch ecosystem to the MLIR ecosystem.

Documentation

82

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

55

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.

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.

CI/CD14pt57

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

Tests18pt80

Test files detected (externals/llvm-external-projects/torch-mlir-dialects/test).

Reproducibility6pt80

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

Project health

64

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Repository metadata5pt60

Repository has a description.

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files27 root entries
  • .github
    Good: CI is configured (.github/workflows/buildAndTest.yml).
  • build_tools
    Good: Environment pinned via build_tools/docker/Dockerfile.
  • docs
  • e2e_testing
  • examples
  • externals
    Good: Test files detected (externals/llvm-external-projects/torch-mlir-dialects/test).
  • include
  • lib
  • python
  • test
  • tools
  • utils
  • .clang-format
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .style.yapf
  • build-requirements.txt
  • CMakeLists.txt
  • LICENSE
    Good: Licensed under Other.
  • pytorch-hash.txt
  • pytorch-requirements.txt
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • setup.py
  • test-requirements.txt
  • torchvision-requirements.txt
  • whl-requirements.txt