Popular for its size, but the engineering basics lag behind the interest.

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 Other.

Engineering

38

CI/CD14pt0

No CI configuration detected in this repository.

If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

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.

Reproducibility6pt70

Lockfile present (MLExamples/Neural_Operators/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (MLExamples/TinyOpenFold/version3_triton/test_correctness.py).

Project health

84

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 manifest6pt100

Dependency manifest found (MLExamples/Neural_Operators/requirements.txt).

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)
  • 86
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 195
    Watchers

Responsiveness

  • 6d 3h
    Median issue response
  • 12h
    Median PR merge time
  • 2
    Open issues
Repository files38 root entries
  • Affinity
  • atomics_openmp
  • benchscripts
  • Doc
  • HIP
  • HIP-OpenMP
  • HIP-Optimizations
  • HIPFort
  • hipifly
  • HIPIFY
    Good: Licensed under Other.
  • HIPStdPar
  • Julia
  • Kokkos
  • Libraries
  • login_info
  • ManagedMemory
  • MLExamples
    Good: Test files detected (MLExamples/TinyOpenFold/version3_triton/test_correctness.py).
    Good: Lockfile present (MLExamples/Neural_Operators/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (MLExamples/Neural_Operators/requirements.txt).
  • MPI-examples
  • Occupancy
  • Omniperf-OpenMP
  • OmniperfExamples
  • Omnitrace
  • Pragma_Examples
  • Profiling-by-example
  • Python
  • Rocgdb
  • rocm-blogs-codes
  • Rocprof
  • rocprof-compute
  • rocprof-tracedecoder
  • rocprofiler-systems
  • Rocprofv3
  • Speedup_Examples
  • tests
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • LICENSE.md
  • 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.