Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 10:47 UTC

ROCm / hipBLAS

[DEPRECATED] Moved to ROCm/rocm-libraries repo

C++ · FortranCustom license★ 152 stars⑂ 86 forkssince Apr 2017View on GitHub ↗

ROCm/hipBLAS holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (77/100) and lowest on Engineering Quality (41/100). It was last updated 14 days ago. 2 contributors account for most of its recent work.

63
overall / 100
Moderate

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

63
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 59 is calibrated to 63 on the published index scale (record calibration 2026-08-02).

Ownership

2,452 followers406 public repossince Aug 2016

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

55Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 14 days ago
0.7/36Commit cadence1/52 weeks with commits
2.7/18Commit volume1 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year1
human_commit_share0.71
days_since_last_push14
active_weeks_last_year1
How it's scored
27/27Ships releases79 releases published
27/36Release recencylatest release 91 days ago
27/27Release cadencea release every ~28.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count79
latest_release_tagrocm-7.2.4
releases_from_tagsno
days_since_latest_release91
mean_days_between_releases28.3
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

69Good · 17% of overall
How it's scored
35.3/60Stars152 stars
16.1/25Forks86 forks
8.5/15Watchers35 watchers
Inputs used
forks86
stars152
watchers35
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

77Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12/22.5Commit distributiontop contributor authored 47% of commits
13.5/13.5Contributor breadth56 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled56
top_contributor_share0.468
How it's scored
42/42Issue resolution100% of issues closed
26.8/30PR acceptance908/1,017 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 16/19 approved changesets -- score normalized to 8
Inputs used
merged_prs908
open_issues0
closed_issues39
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs109
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
24.4/25Owner reach2,452 followers of ROCm
25/25Track record406 public repos, account ~10 yr old
Inputs used
followers2,452
owner_typeOrganization
is_verifiedno
owner_loginROCm
public_repos406
account_age_days3,658

Engineering Quality

Are baseline engineering and documentation practices in place?

41Weak · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests1 out of 25 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://github.com/ROCm/rocm-libraries
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsblas, cuda, rocm, hip
has_wikiyes
homepagehttps://github.com/ROCm/rocm-libraries
docs_sitehttps://github.com/ROCm/rocm-libraries
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests1 out of 25 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6/7.5Code-ReviewFound 16/19 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 5 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
0/7.5Vulnerabilities55 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories89
affected_packages12
assessed_packages93
unassessed_packages0
affected_by_severitycritical 1, high 7, moderate 3, low 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 93 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

50Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history56 of 71 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.789
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingC++ (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance29 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.29
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC++ (statically typed)
53.7/55Manageable file sizes8/346 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes1,754,521
source_files_sampled346
oversized_source_files8
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplessamples
Inputs used
example_dirssamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

152GitHub stars
56contributors
1commits, last 12 months
14days since last push
79releases
2bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 86 ⇿
0Stars
86Forks
76Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0204060801008232017-052021-112026-04
Major 0Minor 2Patch 3

Each point covers 9 days.

OpenSSF Scorecard 4.0 / 10
4.0aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-28 10:47 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests1 out of 25 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 16/19 approved changesets -- score normalized to 8
10Contributorsproject has 5 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities55 existing vulnerabilities detected
All dependencies 93

Full resolved dependency set from the GitHub dependency graph: 0 direct and 93 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
PyPIaccessible-pygments0.0.4indirect
PyPIalabaster0.7.16indirect
PyPIasttokens3.0.0indirect
PyPIattrs24.3.0indirect
PyPIbabel2.14.0indirect
PyPIbeautifulsoup44.12.3indirect
PyPIbreathe4.35.0indirect
PyPIcertifi2024.7.4indirect
PyPIcffi1.16.0indirect
PyPIcharset-normalizer3.3.2indirect
PyPIclick8.1.7indirect
PyPIcomm0.2.2indirect
PyPIcryptography44.0.1indirect
PyPIdebugpy1.8.12indirect
PyPIdecorator5.1.1indirect
PyPIdeprecated1.2.14indirect
PyPIdocutils0.21.2indirect
PyPIexceptiongroup1.2.2indirect
PyPIexecuting2.1.0indirect
PyPIfastjsonschema2.19.1indirect
PyPIgitdb4.0.11indirect
PyPIgitpython3.1.43indirect
PyPIgreenlet3.1.1indirect
PyPIidna3.7indirect
PyPIimagesize1.4.1indirect
PyPIimportlib-metadata8.6.1indirect
PyPIipykernel6.29.5indirect
PyPIipython8.31.0indirect
PyPIjedi0.19.2indirect
PyPIjinja23.1.6indirect
PyPIjsonschema4.23.0indirect
PyPIjsonschema-specifications2024.10.1indirect
PyPIjupyter-cache1.0.1indirect
PyPIjupyter-client8.6.3indirect
PyPIjupyter-core5.7.2indirect
PyPImarkdown-it-py3.0.0indirect
PyPImarkupsafe2.1.5indirect
PyPImatplotlib-inline0.1.7indirect
PyPImdit-py-plugins0.4.0indirect
PyPImdurl0.1.2indirect
PyPImyst-nb1.1.2indirect
PyPImyst-parser3.0.1indirect
PyPInbclient0.10.2indirect
PyPInbformat5.10.4indirect
PyPInest-asyncio1.6.0indirect
PyPIpackaging24.0indirect
PyPIparso0.8.4indirect
PyPIpexpect4.9.0indirect
PyPIplatformdirs4.3.6indirect
PyPIprompt-toolkit3.0.50indirect
PyPIpsutil6.1.1indirect
PyPIptyprocess0.7.0indirect
PyPIpure-eval0.2.3indirect
PyPIpycparser2.22indirect
PyPIpydata-sphinx-theme0.16.1indirect
PyPIpygithub2.3.0indirect
PyPIpygments2.17.2indirect
PyPIpyjwt2.8.0indirect
PyPIpynacl1.5.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpyyaml6.0.1indirect
PyPIpyzmq26.2.0indirect
PyPIreferencing0.36.1indirect
PyPIrequests2.32.4indirect
PyPIrocm-docs-core1.21.1indirect
PyPIrpds-py0.22.3indirect
PyPIsix1.17.0indirect
PyPIsmmap5.0.1indirect
PyPIsnowballstemmer2.2.0indirect
PyPIsoupsieve2.5indirect
PyPIsphinx7.3.7indirect
PyPIsphinx-book-theme1.1.2indirect
PyPIsphinx-copybutton0.5.2indirect
PyPIsphinx-design0.5.0indirect
PyPIsphinx-external-toc1.0.1indirect
PyPIsphinx-notfound-page1.0.0indirect
PyPIsphinxcontrib-applehelp1.0.8indirect
PyPIsphinxcontrib-devhelp1.0.6indirect
PyPIsphinxcontrib-htmlhelp2.0.5indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp1.0.7indirect
PyPIsphinxcontrib-serializinghtml1.1.10indirect
PyPIsqlalchemy2.0.37indirect
PyPIstack-data0.6.3indirect
PyPItabulate0.9.0indirect
PyPItomli2.0.1indirect
PyPItornado6.5.1indirect
PyPItraitlets5.14.3indirect
PyPItyping-extensions4.11.0indirect
PyPIurllib32.5.0indirect
PyPIwcwidth0.2.13indirect
PyPIwrapt1.16.0indirect
PyPIzipp3.21.0indirect
Dependency advisories 12

This repository publishes no package the index resolves, so its own dependency graph was assessed — 93 packages, which also include development and test pins that never ship: 12 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
gitpython3.1.43indirectcritical263.1.58
click8.1.7indirecthigh18.3.3
cryptography44.0.1indirecthigh1150.0.0
jupyter-core5.7.2indirecthigh25.8.1
pyjwt2.8.0indirecthigh112.13.0
soupsieve2.5indirecthigh42.8.4
tornado6.5.1indirecthigh186.5.7
urllib32.5.0indirecthigh82.7.0
idna3.7indirectmoderate23.15
pynacl1.5.0indirectmoderate23.6.1
requests2.32.4indirectmoderate22.33.0
pygments2.17.2indirectlow22.20.0

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics.