Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 03:37 UTC

rapidsai / rapidsmpf

C++ · Cython · PythonApache-2.0★ 35 stars⑂ 42 forkssince Nov 2024View on GitHub ↗

rapidsai/rapidsmpf holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Vitality (96/100) and lowest on Community & Adoption (63/100). It was last updated today. 3 contributors account for most of its recent work.

94
overall / 100
Exceptional

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.

94
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 81 is calibrated to 94 on the published index scale (record calibration 2026-08-02).

Ownership

RAPIDSOrganization · verified domain
2,490 followers133 public repossince Oct 2018

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?

96Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
35.3/36Commit cadence51/52 weeks with commits
18/18Commit volume513 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year513
human_commit_share0.99
days_since_last_push0
active_weeks_last_year51
How it's scored
27/27Ships releases6 releases published
36/36Release recencylatest release 21 days ago
19.8/27Release cadencea release every ~51.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count6
latest_release_tagv26.08.01
releases_from_tagsno
days_since_latest_release21
mean_days_between_releases51.7
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?

63Moderate · 17% of overall
How it's scored
24.8/60Stars35 stars
13.4/25Forks42 forks
5.8/15Watchers12 watchers
Inputs used
forks42
stars35
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

85Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
17/22.5Commit distributiontop contributor authored 25% of commits
13.5/13.5Contributor breadth31 contributors
10/10OpenSSF Scorecard: Contributorsproject has 42 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled31
top_contributor_share0.246
How it's scored
31.2/42Issue resolution74% of issues closed
26.2/30PR acceptance823/942 decided PRs merged
13/13Newcomer PR acceptance4/4 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 22/25 approved changesets -- score normalized to 8
Inputs used
merged_prs823
open_issues63
closed_issues182
prs_merged_7d6
prs_decided_7d7
prs_merged_30d38
prs_decided_30d40
issue_closed_ratio0.743
closed_unmerged_prs119
first_time_authors_30d2
first_time_prs_merged_30d4
first_time_prs_decided_30d4
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
24.4/25Owner reach2,490 followers of rapidsai
25/25Track record133 public repos, account ~7 yr old
Inputs used
followers2,490
owner_typeOrganization
is_verifiedyes
owner_loginrapidsai
public_repos133
account_age_days2,903

Engineering Quality

Are baseline engineering and documentation practices in place?

87Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff], [tool.isort])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests25 out of 27 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://docs.nvidia.com/rapidsmpf
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://docs.nvidia.com/rapidsmpf
docs_sitehttps://docs.nvidia.com/rapidsmpf
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

69Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
6/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.2/2.5CI-Tests25 out of 27 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6/7.5Code-ReviewFound 22/25 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 42 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.9
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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.

75Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.nvidia.com/llms.txt)
40/40Legible commit history89 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.nvidia.com/llms.txt
legible_history_share0.899
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapdocs/Makefile
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff], [tool.isort])
11/11Static type checkingC++ (statically typed)
10/10Reproducible environmentdevcontainer, Dockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_filesdocs/Makefile
has_devcontaineryes
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeC++ (statically typed)
55/55Manageable file sizes0/263 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes59,855
source_files_sampled263
oversized_source_files0
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 examplesexamples, recipes
Inputs used
example_dirsexamples, recipes
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

35GitHub stars
31contributors
513commits, last 12 months
0days since last push
6releases
3bus factor
63open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 14 authors (cap 12)
  • Could not fetch pypi package 'rapidsmpf' from its registry
  • Could not fetch pypi package 'librapidsmpf' from its registry
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 42 ⇿
0Stars
42Forks
6Releases

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.

010203040504122025-042026-012026-09
Major 0Minor 5Patch 1

Each point covers 2 days.

OpenSSF Scorecard 6.9 / 10
6.9aggregate

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-09-17 03:36 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests25 out of 27 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 22/25 approved changesets -- score normalized to 8
10Contributorsproject has 42 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
PyPIlibrmm==26.12.*,>=0.0.0a0python/librapidsmpf/pyproject.toml
PyPIlibucxx==0.53.*,>=0.0.0a0python/librapidsmpf/pyproject.toml
PyPIlibrapidsmpf==26.12.*,>=0.0.0a0python/rapidsmpf/pyproject.toml
PyPIrmm==26.12.*,>=0.0.0a0python/rapidsmpf/pyproject.toml
PyPIucxx==0.53.*,>=0.0.0a0python/rapidsmpf/pyproject.toml
All dependencies 10

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

RegistryPackageVersionRelation
PyPIlibrapidsmpfdirect
PyPIlibrmmdirect
PyPIlibucxxdirect
PyPIrmmdirect
PyPIucxxdirect
PyPIcupy-cuda13xindirect
PyPInumpyindirect
PyPIrapids-build-backendindirect
PyPIrayindirect
PyPIscikit-build-coreindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.