rocm/therock
Grade a repo

0

/ 100

GradeB

Good community traction and solid fundamentals. Nearly in the top tier.

Top 26% of 5,156 graded repos

The HIP Environment and ROCm Kit - A lightweight open source build system for HIP and ROCm

Documentation95
Engineering69
Health100
Python1,098MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add `pull_request:` to the workflow `on:` triggers.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

95

Contributing guide5pt84

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

69

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

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

Tests18pt80

Test files detected (build_tools/github_actions/test_executable_scripts/test_amdsmi.py).

Reproducibility6pt82

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

Linting and formatting5pt100

Linter or formatter configured (build_tools/third_party/implib/.pylintrc).

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)
  • 264
    Forks
  • 4
    Releaseslatest 2mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,098
    Watchers

Responsiveness

  • 4h
    Median issue response
  • 2h
    Median PR merge time
  • 973
    Open issues
Repository files45 root entries
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/build_portable_linux_python_packages.yml).
    Good: Dependabot configured for github-actions.
  • base
  • build_tools
    Good: Test files detected (build_tools/github_actions/test_executable_scripts/test_amdsmi.py).
    Good: Linter or formatter configured (build_tools/third_party/implib/.pylintrc).
  • cmake
  • comm-libs
  • compiler
  • core
  • dctools
  • debug-tools
  • dockerfiles
  • docs
  • emulation
  • examples
  • external-builds
  • math-libs
  • media-libs
  • ml-libs
  • patches
  • profiler
  • skills
  • storage-libs
  • test_tools
  • tests
  • third-party
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .pre-commit-config.yaml
  • BUILD_TOPOLOGY.toml
  • CLAUDE.md
  • CMakeLists.txt
  • CMakePresets.json
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
    Good: Contributing guide includes code examples.
  • FLAGS.cmake
  • gitleaks.toml
  • LICENSE
    Good: Licensed under MIT.
  • 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.
  • RELEASES.md
  • requirements-test.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • ROADMAP.md
  • rocm-libraries
  • rocm-systems
  • SUPPORTED_GPUS.md
  • version.json
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/rocm/therock)](https://www.repo-grade.com/report/rocm/therock)

More graded Python repos