rocm/rocm-systems

0

/ 100

Documentation88
Engineering88
Health100
C++4121d ago
Grade a repo

Polished and well engineered. Punching above its star count.

super repo for rocm systems projects

Documentation

88

README12pt80

README is present.

Contributing guide5pt89

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

88

Tests18pt80

Test files detected (.github/scripts/tests).

CI/CD14pt85

CI is configured (.github/workflows/abi-compliance-check.yml).

Linting and formatting5pt100

Linter or formatter configured (emulation/mirage/dashboard/web/eslint.config.js).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (.github/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)
  • 277
    Forks
  • 11
    Releaseslatest 1mo ago

Community

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

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 923
    Open issues
Repository files17 root entries
  • .dvc
    Good: .gitignore present.
  • .github
    Good: Test files detected (.github/scripts/tests).
    Good: CI is configured (.github/workflows/abi-compliance-check.yml).
    Good: Lockfile present (.github/requirements.txt). Installs are reproducible.
    Good: Dependabot covers 12 ecosystems (github-actions, pip, pip, pip, pip, pip, pip, pip, pip, pip, pip, pip). Dependencies stay current.
    Good: Issue or PR templates present.
    Good: Dependency manifest found (.github/requirements.txt).
  • docs
  • emulation
    Good: A license file is present.
    Good: Linter or formatter configured (emulation/mirage/dashboard/web/eslint.config.js).
    Good: Environment pinned via emulation/Dockerfile.
  • experimental
  • profilers
  • projects
    Good: Code of conduct present.
    Good: Security policy present.
  • python
  • shared
  • test
  • .dvcignore
  • .git-blame-ignore-revs
  • .gitignore
  • .gitmodules
  • .pre-commit-config.yaml
  • 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.
  • 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.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.