Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 21:09 UTC

ruby / setup-ruby

An action to download a prebuilt Ruby and add it to the PATH in 5 seconds

JavaScript · RubyMIT★ 984 stars⑂ 368 forkssince Jan 2020View on GitHub ↗

ruby/setup-ruby holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on AI Readiness (18/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

2,075 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
npmsetup-rubypoints to another repo — not scored0.0.1-security611544 days ago

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
27.7/36Commit cadence40/52 weeks with commits
18/18Commit volume131 commits in the last year
10/10OpenSSF Scorecard: Maintained21 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year131
human_commit_share
days_since_last_push4
active_weeks_last_year40

Release discipline

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

74Good · 17% of overall
How it's scored
48.5/60Stars984 stars
21.4/25Forks368 forks
8/15Watchers29 watchers
Inputs used
forks368
stars984
watchers29
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

74Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.5/22.5Commit distributiontop contributor authored 58% of commits
13.5/13.5Contributor breadth77 contributors
10/10OpenSSF Scorecard: Contributorsproject has 49 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled77
top_contributor_share0.578
How it's scored
40.9/42Issue resolution97% of issues closed
24.9/30PR acceptance356/429 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 20/24 approved changesets -- score normalized to 8
Inputs used
merged_prs356
open_issues11
closed_issues412
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.974
closed_unmerged_prs73
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
23.8/25Owner reach2,075 followers of ruby
25/25Track record190 public repos, account ~16 yr old
Inputs used
followers2,075
owner_typeOrganization
is_verified
owner_loginruby
public_repos190
account_age_days5,989
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

51Moderate · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests20 out of 22 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicsmri, jruby, truffleruby, actions, prebuilt-ruby, prebuilt-rubies, ruby-action
has_wikino
homepagehttps://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby
docs_sitehttps://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 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
2.2/2.5CI-Tests20 out of 22 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 20/24 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 49 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.5/2.5Licenselicense file detected
7.5/7.5Maintained21 commit(s) and 6 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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities15 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories1 affected: json 2.2.0 (high 7.5)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,184 days ago
Inputs used
sourceosv
advisories16
affected_packages5
assessed_packages50
unassessed_packages2
affected_by_severityhigh 5
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 50 resolved dependencies against OSV. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

18Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilesyarn.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/12 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes13,780
source_files_sampled12
oversized_source_files0

Key facts

984GitHub stars
77contributors
131commits, last 12 months
4days since last push
100releases
1bus factor
11open issues
npm, RubyGemspackage ecosystems

Data collection warnings

  • npm package 'setup-ruby' points at a different repository (npm/security-holder); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 5.2 / 10
5.2aggregate

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-07-20 21:08 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests20 out of 22 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 20/24 approved changesets -- score normalized to 8
10Contributorsproject has 49 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained21 commit(s) and 6 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities15 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
RubyGemsrakeGemfile
RubyGemspathGemfile
RubyGemsjson2.2.0Gemfile
npm@actions/cache^5.0.3package.json
npm@actions/core^2.0.2package.json
npm@actions/exec^2.0.0package.json
npm@actions/io^2.0.0package.json
npm@actions/tool-cache^3.0.0package.json
npmlinux-os-info^2.0.0package.json
npmsemver^7.7.3package.json
All dependencies 52

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

RegistryPackageVersionRelation
npm@actions/cache5.0.3direct
npm@actions/core1.11.1direct
npm@actions/core2.0.2direct
npm@actions/exec1.1.1direct
npm@actions/exec2.0.0direct
npm@actions/io1.1.3direct
npm@actions/io2.0.0direct
npm@actions/tool-cache3.0.0direct
npmlinux-os-info2.0.0direct
npmsemver6.3.1direct
npmsemver7.7.3direct
RubyGemsjson2.2.0direct
RubyGemspathdirect
RubyGemsrakedirect
npm@actions/glob0.5.0indirect
npm@actions/http-client2.2.3indirect
npm@actions/http-client3.0.1indirect
npm@azure/abort-controller1.1.0indirect
npm@azure/abort-controller2.1.2indirect
npm@azure/core-auth1.10.1indirect
npm@azure/core-client1.10.1indirect
npm@azure/core-http-compat2.3.1indirect
npm@azure/core-lro2.7.2indirect
npm@azure/core-paging1.6.2indirect
npm@azure/core-rest-pipeline1.22.2indirect
npm@azure/core-tracing1.3.1indirect
npm@azure/core-util1.13.1indirect
npm@azure/core-xml1.5.0indirect
npm@azure/logger1.3.0indirect
npm@azure/storage-blob12.30.0indirect
npm@azure/storage-common12.2.0indirect
npm@fastify/busboy2.1.1indirect
npm@protobuf-ts/runtime2.11.1indirect
npm@protobuf-ts/runtime-rpc2.11.1indirect
npm@typespec/ts-http-runtime0.3.2indirect
npm@vercel/ncc0.38.4indirect
npmagent-base7.1.4indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.12indirect
npmconcat-map0.0.1indirect
npmdebug4.4.3indirect
npmevents3.3.0indirect
npmfast-xml-builder1.0.0indirect
npmfast-xml-parser5.4.1indirect
npmhttp-proxy-agent7.0.2indirect
npmhttps-proxy-agent7.0.6indirect
npmminimatch3.1.4indirect
npmms2.1.3indirect
npmstrnum2.1.2indirect
npmtslib2.8.1indirect
npmtunnel0.0.6indirect
npmundici5.29.0indirect
Dependency advisories 5

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: 5 carry known advisories, of which 1 are direct. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
json2.2.0directhigh12.3.0
brace-expansion1.1.12indirecthigh25.0.7
fast-xml-builder1.0.0indirecthigh11.1.7
fast-xml-parser5.4.1indirecthigh35.7.0
undici5.29.0indirecthigh98.5.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.16.0 — full methodology · metrics wiki.

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