Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 05:24 UTC

Shopify / ruby

The Ruby Programming Language [mirror]

Ruby · CCustom license★ 52 stars⑂ 15 forkssince Sep 2019forkView on GitHub ↗
KindLibraryCommand-line toolhow this is determined

Shopify/ruby holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (84/100) and lowest on Community & Adoption (32/100). It was last updated today. 6 contributors account for most of its recent work.

80
overall / 100
Excellent

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.

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

Ownership

ShopifyOrganization · verified domain
8,607 followers1,229 public repossince Apr 2008

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iorubypoints to another repo — not scored0.0.282178 days agolanguagerubyruntimedevelopment-tools
crates.iojitpoints to another repo — not scored0.9.154344115 days agocompileinterpreterjitcompiler
RubyGemsipaddrpoints to another repo — not scored1.2.9-12147 days ago
RubyGemstmpdirpoints to another repo — not scored0.3.1-7640 days ago
RubyGemsenglishpoints to another repo — not scored0.8.1-5323 days ago
RubyGemsfileutilspoints to another repo — not scored1.8.0-17324 days ago
RubyGemsetcpoints to another repo — not scored1.4.6-12430 days ago
RubyGemserbpoints to another repo — not scored6.0.7-5245 days ago
RubyGemsdatepoints to another repo — not scored3.5.1-34282 days ago
RubyGemsjsonpoints to another repo — not scored3.0.2-2479 days ago
RubyGemszlibpoints to another repo — not scored3.2.3-16198 days ago
RubyGemsfcntlpoints to another repo — not scored1.3.0-7373 days ago
RubyGemspsychpoints to another repo — not scored5.5.0-15729 days ago

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
35.3/36Commit cadence51/52 weeks with commits
18/18Commit volume7,456 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year7,456
human_commit_share0.98
days_since_last_push0
active_weeks_last_year51
How it's scored
16.2/27Ships releases11 version tags (no GitHub releases)
27/36Release recencylatest release 122 days ago
12.6/27Release cadencea release every ~171.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count11
latest_release_tagv4.0.5
releases_from_tagsyes
days_since_latest_release122
mean_days_between_releases171.8
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?

32At Risk · 17% of overall
How it's scored
27.7/60Stars52 stars
9.6/25Forks15 forks
5.6/15Watchers11 watchers
Inputs used
forks15
stars52
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, travis-ci.com
has_pull_request_templateno

Sustainability & Governance

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

84Excellent · 23% of overall
How it's scored
48.6/54Bus factor6 contributor(s) cover half of all commits
16.5/22.5Commit distributiontop contributor authored 27% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 113 contributing companies or organizations
Inputs used
bus_factor6
contributors_sampled99
top_contributor_share0.268
How it's scored
33.4/42Issue resolution80% of issues closed
21.9/30PR acceptance354/484 decided PRs merged
6.5/13Newcomer PR acceptance1/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs354
open_issues110
closed_issues427
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio0.795
closed_unmerged_prs130
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
25/25Owner reach8,607 followers of Shopify
25/25Track record1,229 public repos, account ~18 yr old
Inputs used
followers8,607
owner_typeOrganization
is_verifiedyes
owner_loginShopify
public_repos1,229
account_age_days6,724

Engineering Quality

Are baseline engineering and documentation practices in place?

69Good · 19% of overall
How it's scored
24/24CI workflows39 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://www.ruby-lang.org/
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://www.ruby-lang.org/
docs_sitehttps://www.ruby-lang.org/
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 113 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 14 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
5/5SASTSAST tool detected: CodeQL
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
4.5/7.5Vulnerabilities4 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.1
Excluded from scoring (no data or not applicable): CI-Tests, 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.

73Good · 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://www.ruby-lang.org/llms.txt)
35.9/40Legible commit history66 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.ruby-lang.org/llms.txt
legible_history_share0.673
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstraptest/net/fixtures/Makefile
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice32 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance2 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, Gemfile.lock
has_dockerfileyes
typed_languageno
bootstrap_filestest/net/fixtures/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.32
toolchain_manifestsCargo.toml, gc/mmtk/Cargo.toml, jit/Cargo.toml, test/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, yjit/Cargo.toml, yjit/bindgen/Cargo.toml, zjit/Cargo.toml, zjit/bindgen/Cargo.toml
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable codeRuby without a type-check config
54.1/55Manageable file sizes135/8,503 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes3,114,306
source_files_sampled8,503
oversized_source_files135
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, sample
Inputs used
example_dirsexamples, sample
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

52GitHub stars
99contributors
7,456commits, last 12 months
0days since last push
11releases
6bus factor
110open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Community profile unavailable
  • crates package 'ruby' points at a different repository (https://github.com/nyar-vm/rusty-ruby); excluded from ecosystem scoring
  • crates package 'jit' points at a different repository (http://wwww.rustdox.com/TomBebbington/jit.rs/); excluded from ecosystem scoring
  • Could not fetch crates package 'yjit' from its registry
  • Could not fetch crates package 'zjit' from its registry
  • rubygems package 'ipaddr' points at a different repository (https://github.com/ruby/ipaddr); excluded from ecosystem scoring
  • rubygems package 'tmpdir' points at a different repository (https://github.com/ruby/tmpdir); excluded from ecosystem scoring
  • rubygems package 'english' points at a different repository (https://github.com/ruby/English); excluded from ecosystem scoring
  • rubygems package 'fileutils' points at a different repository (https://github.com/ruby/fileutils); excluded from ecosystem scoring
  • Could not fetch crates package 'mmtk_ruby' from its registry
  • rubygems package 'etc' points at a different repository (https://github.com/ruby/etc); excluded from ecosystem scoring
  • rubygems package 'erb' points at a different repository (https://github.com/ruby/erb); excluded from ecosystem scoring
  • rubygems package 'date' points at a different repository (https://github.com/ruby/date); excluded from ecosystem scoring
  • rubygems package 'json' points at a different repository (https://github.com/ruby/json); excluded from ecosystem scoring
  • rubygems package 'zlib' points at a different repository (https://github.com/ruby/zlib); excluded from ecosystem scoring
  • rubygems package 'fcntl' points at a different repository (https://github.com/ruby/fcntl); excluded from ecosystem scoring
  • rubygems package 'psych' points at a different repository (https://github.com/ruby/psych); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 15 ⇿
0Stars
15Forks
11Releases

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.

03581013151522020-082023-092026-09
Major 1Minor 0Patch 5

Each point covers 6 days.

OpenSSF Scorecard 6.1 / 10
6.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-09-19 05:24 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 113 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 14 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
10SASTSAST tool detected: CodeQL
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6Vulnerabilities4 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
crates.ioyjitCargo.toml
crates.iozjitCargo.toml
crates.iocapstone0.14.0yjit/Cargo.toml
crates.iojit0.1.0yjit/Cargo.toml
crates.iocapstone0.14.0zjit/Cargo.toml
crates.iojit0.1.0zjit/Cargo.toml
crates.iolibc0.2gc/mmtk/Cargo.toml
crates.iolog0.4.14gc/mmtk/Cargo.toml
crates.ioenv_logger0.11.3gc/mmtk/Cargo.toml
crates.ioonce_cell1.17.0gc/mmtk/Cargo.toml
crates.ioatomic_refcell0.1.9gc/mmtk/Cargo.toml
crates.ioprobe0.5gc/mmtk/Cargo.toml
crates.iosysinfo0.32.0gc/mmtk/Cargo.toml
crates.iommtkgc/mmtk/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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 statisticscrates.io, RubyGems.