rocm/amdmigraphx

0

/ 100

Documentation70
Engineering70
Health100
C++310MIT1d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

AMD's graph optimization engine.

Documentation

70

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.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

70

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/CD14pt57

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

Tests18pt80

Test files detected (test).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

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)
  • 138
    Forks
  • 64
    Releaseslatest 4y ago

Community

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

Responsiveness

  • 57d 18h
    Median issue response
  • 1d 8h
    Median PR merge time
  • 341
    Open issues
Repository files28 root entries
  • .azuredevops
  • .claude
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/ci.yaml).
    Good: Dependabot covers 5 ecosystems (pip, pip, pip, pip, pip). Dependencies stay current.
    Good: Issue or PR templates present.
  • cmake
  • docs
  • examples
  • src
  • test
    Good: Test files detected (test).
  • tools
  • .clang-format
  • .clang-tidy
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .readthedocs.yaml
  • AGENTS.md
  • CHANGELOG.md
  • CMakeLists.txt
  • codecov.yml
  • dev-requirements.txt
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • hip-clang.docker
  • Jenkinsfile
  • LICENSE
    Good: Licensed under MIT.
  • rbuild.ini
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    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.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • SECURITY.md
    Good: Security policy present.