ROCm/rocm-libraries

super repo for rocm libraries

Owned by AMD

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

ROCm/rocm-libraries has 450+ stars and 400+ forks on GitHub, is written in Assembly, 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
Added to GitGenius on October 12th, 2026
Created on April 23rd, 2025
Open Issues & Pull Requests: 1,434 (-1)
GitHub issues: Enabled
Number of forks: 437
Total Stargazers: 453 (+1)
Total Subscribers: 9 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 hours
Mean response time: 15.2 days
90th percentile: 32.1 days
Tracked items: 884

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 88% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "code-regression" is answered fastest, typically in under an hour, while "project: rocblas" waits about 2 days. 46% 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: 696
New in 7 days: 49
Closed in 7 days: 25
Avg open age: 165 days
Stale 30+ days: 505
Stale 90+ days: 321

Recent activity

Opened in 7 days: 48
Closed in 7 days: 25
Comments in 7 days: 68
Events in 7 days: 289

Top labels

  • project: hipdnn (130)
  • project: miopen (88)
  • project: hipblaslt (87)
  • status: triage (82)
  • monitoring (61)
  • project: composablekernel (60)
  • code-regression (59)
  • bump-pr (58)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

ROCm Libraries is a super-repository that consolidates multiple ROCm-related libraries and shared components into a single unified codebase.

The project addresses the fragmentation of ROCm library development across separate repositories by bringing them together under one roof. This consolidation enables unified build and test workflows, allows libraries to share tooling and CI infrastructure, and improves integration and visibility across ROCm library teams. Developers work against a single source of truth rather than coordinating changes across multiple independent repositories.

Teams adopting this approach should understand that component migration is ongoing. Some libraries have completed full migration and integration, making the super-repository the authoritative source. Others are in active migration, and contributors are asked to develop against the super-repository rather than individual component repositories during this period. A third category of components remains in pending status, with their original individual repositories still serving as the source of truth. The project uses TheRock build system for multi-component testing. Developers should check the component status table in the README to determine which libraries have stabilized in the super-repository and which still rely on legacy CI systems or individual repositories.

The project shows active consolidation work with components at different stages of integration. Migration efforts are underway with clear communication about where development should occur during transition phases. The maintenance of legacy CI status indicators alongside migration progress suggests sustained attention to both completing the consolidation and maintaining stability during the transition period.