Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 06:51 UTC

ruby / rubygems

Library packaging and distribution for Ruby.

RubyCustom license★ 3,952 stars⑂ 1,932 forkssince Apr 2010View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

ruby/rubygems holds a health index of 99 out of 100, placing it in the Exceptional band. It scores highest on Vitality (100/100) and lowest on AI Readiness (63/100). It was last updated 6 days ago. 4 contributors account for most of its recent work.

99
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.

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

Ownership

2,085 followers190 public repossince Feb 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsbundler4.0.18-4288 days ago
RubyGemsrubygems-update4.0.18-3208 days ago

Metrics by category

Vitality

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

100Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recencylast push 6 days ago
36/36Commit cadence52/52 weeks with commits
18/18Commit volume1,736 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,736
human_commit_share0.93
days_since_last_push6
active_weeks_last_year52

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 8 days ago
27/27Release cadencea release every ~7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv4.0.18
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases7
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?

94Exceptional · 17% of overall
How it's scored
58.3/60Stars3,952 stars
25/25Forks1,932 forks
12.3/15Watchers164 watchers
Inputs used
forks1,932
stars3,952
watchers164
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/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_templateyes
How it's scored
80/80Total downloads4,255,644,028 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesbundler, rubygems-update
dependents
ecosystemsrubygems
total_downloads4,255,644,028
monthly_downloads
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

89Excellent · 23% of overall
How it's scored
43.2/54Bus factor4 contributor(s) cover half of all commits
16.6/22.5Commit distributiontop contributor authored 26% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 107 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled99
top_contributor_share0.264
How it's scored
40.1/42Issue resolution95% of issues closed
26.1/30PR acceptance4,920/5,659 decided PRs merged
13/13Newcomer PR acceptance3/3 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/11 approved changesets -- score normalized to 0
Inputs used
merged_prs4,920
open_issues168
closed_issues3,502
prs_merged_7d1
prs_decided_7d2
prs_merged_30d47
prs_decided_30d52
issue_closed_ratio0.954
closed_unmerged_prs739
first_time_authors_30d2
first_time_prs_merged_30d3
first_time_prs_decided_30d3
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
23.9/25Owner reach2,085 followers of ruby
25/25Track record190 public repos, account ~16 yr old
Inputs used
followers2,085
owner_typeOrganization
is_verified
owner_loginruby
public_repos190
account_age_days6,013
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on rubygems
35/35Publish recencylatest publish 8 days ago
20/20Version history428 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbundler, rubygems-update
ecosystemsrubygems
any_deprecatedno
min_days_since_publish8

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows11 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests11 out of 11 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://rubygems.org/
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsrubygems, ruby, package-manager
has_wikino
homepagehttps://rubygems.org/
docs_sitehttps://rubygems.org/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

85Excellent · 16% of overall

Security posture

81Excellent
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests11 out of 11 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/11 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 107 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
4.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
5/5SASTSAST tool is run on all commits
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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate8.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. 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
advisories0
affected_packages0
assessed_packages50
unassessed_packages0
affected_by_severitynone
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 50 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.

63Moderate · 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 history87 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.935
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstraptest/rubygems/test_gem_ext_cargo_builder/custom_name/ext/custom_name_lib/Cargo.toml, test/rubygems/test_gem_ext_cargo_builder/rust_ruby_example/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
10/10Reproducible environmentdevcontainer, Dockerfile, lockfile
10/10Demonstrated agent practice44 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance7 of the last 100 commits are automated dependency updates
9/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, Gemfile.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontaineryes
has_linter_configyes
typecheck_configs
agent_commit_share0.44
toolchain_manifeststest/rubygems/test_gem_ext_cargo_builder/custom_name/ext/custom_name_lib/Cargo.toml, test/rubygems/test_gem_ext_cargo_builder/rust_ruby_example/Cargo.toml
dependency_bot_commit_share0.07
How it's scored
0/45Type-checkable codeRuby without a type-check config
54.7/55Manageable file sizes4/799 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes111,522
source_files_sampled799
oversized_source_files4

Key facts

3,952GitHub stars
99contributors
1,736commits, last 12 months
6days since last push
100releases
4bus factor
168open issues
package ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 1,932 ⇿
0Stars
1,932Forks
100Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

5001,0001,5002,0001,932142019-082023-022026-08
Major 1Minor 2Patch 45

Each point covers 7 days.

OpenSSF Scorecard 8.1 / 10
8.1aggregate

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-13 06:51 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests11 out of 11 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/11 approved changesets -- score normalized to 0
10Contributorsproject has 107 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 50

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

RegistryPackageVersionRelation
crates.ioaho-corasick0.7.20indirect
crates.iobindgen0.72.1indirect
crates.iobitflags2.3.3indirect
crates.iocexpr0.6.0indirect
crates.iocfg-if1.0.0indirect
crates.ioclang-sys1.4.0indirect
crates.ioeither1.15.0indirect
crates.ioglob0.3.0indirect
crates.ioitertools0.13.0indirect
crates.iolazy_static1.4.0indirect
crates.iolibc0.2.138indirect
crates.iolibloading0.7.4indirect
crates.iomemchr2.5.0indirect
crates.iominimal-lexical0.2.1indirect
crates.ionom7.1.1indirect
crates.ioproc-macro21.0.106indirect
crates.ioquote1.0.32indirect
crates.iorb-sys0.9.128indirect
crates.iorb-sys-build0.9.128indirect
crates.ioregex1.7.0indirect
crates.ioregex-syntax0.6.28indirect
crates.iorustc-hash2.1.2indirect
crates.ioshell-words1.1.0indirect
crates.ioshlex1.3.0indirect
crates.iosyn2.0.28indirect
crates.iounicode-ident1.0.5indirect
crates.iowinapi0.3.9indirect
crates.iowinapi-i686-pc-windows-gnu0.4.0indirect
crates.iowinapi-x86_64-pc-windows-gnu0.4.0indirect
RubyGemserubi1.13.1indirect
RubyGemsjruby-jars10.0.0.1indirect
RubyGemsjruby-rack1.2.7indirect
RubyGemsnetrc0.11.0indirect
RubyGemsostruct0.6.3indirect
RubyGemsparallel1.26.3indirect
RubyGemsprism1.3.0indirect
RubyGemsrake13.3.0indirect
RubyGemsrbi0.2.2indirect
RubyGemsrexml3.4.2indirect
RubyGemsrubyzip3.3.0indirect
RubyGemssorbet0.5.11725indirect
RubyGemssorbet-runtime0.5.11725indirect
RubyGemssorbet-static0.5.11725indirect
RubyGemssorbet-static-and-runtime0.5.11725indirect
RubyGemsspoom1.5.0indirect
RubyGemstapioca0.16.6indirect
RubyGemsthor1.4.0indirect
RubyGemswarbler2.1.0indirect
RubyGemsyard0.9.44indirect
RubyGemsyard-sorbet0.9.0indirect
Dependency advisories 0

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

No known advisories affect the assessed dependencies.

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.31.0 — full methodology · metrics wiki.

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