logo

ROCm/rocm-systems

super repo for rocm systems projects

Owned by AMD

View on GitHub ↗Jump to charts ↓Open shareable report →

ROCm/rocm-systems has 500+ stars and 450+ forks on GitHub, is written in C++, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 40 minutes ago
Type:Server / PlatformCategory(s):GPU, Accelerators & HPCMLOps & Model DeploymentSystems, Hardware & HPC
Added to GitGenius on October 12th, 2026
Created on April 7th, 2025
Open Issues & Pull Requests: 1,500 (+0)
GitHub issues: Enabled
Number of forks: 454
Total Stargazers: 537 (+0)
Total Subscribers: 5 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.7 hours
Mean response time: 9.0 days
90th percentile: 16.8 days
Tracked items: 726

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

159 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 90% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "project: rocjitsu" is answered fastest, typically in under an hour, while "Under Investigation" waits about 11 days. 35% of tracked open issues have had no activity in three months. Only 43% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 621
New in 7 days: 46
Closed in 7 days: 17
Avg open age: 165 days
Stale 30+ days: 427
Stale 90+ days: 273

Recent activity

Opened in 7 days: 43
Closed in 7 days: 17
Comments in 7 days: 45
Events in 7 days: 262

Top labels

  • project: rocjitsu (117)
  • status: triage (106)
  • project: rocprofiler-compute (63)
  • bug (59)
  • Under Investigation (57)
  • code-regression (44)
  • bump-pr (42)
  • platform: Linux (42)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

ROCm Systems is a super-repository that consolidates multiple ROCm systems projects into a single unified codebase to streamline development, continuous integration, and integration workflows.

The project addresses the fragmentation of ROCm systems development across multiple separate repositories by bringing related projects together under one umbrella. This consolidation approach simplifies dependency management, CI pipeline configuration, and cross-project integration. The initial focus targets projects required for building PyTorch, establishing a foundation for broader systems development within the ROCm ecosystem.

Developers should adopt this repository if they are working on ROCm systems projects that have completed migration to the super-repo, as those are now considered the authoritative source. The tool suits teams building PyTorch with ROCm or contributing to the underlying systems infrastructure. For projects still in migration or pending status, developers should continue using the individual repositories as the source of truth until integration is complete. The README explicitly discourages submitting pull requests to individual project repositories for work that is in progress on the super-repo, directing contributors to develop against the consolidated codebase instead.

The project maintains a clear migration status tracking system distinguishing between completed integrations, ongoing migrations, and pending work. Development activity spans multiple ROCm systems projects with varying stages of consolidation, indicating active coordination across different components of the systems stack.