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

cucumber / cucumber-ruby

Cucumber for Ruby. It's amazing!

Ruby · GherkinMIT★ 5,215 stars⑂ 1,118 forkssince Apr 2008View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

cucumber/cucumber-ruby holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Community & Adoption (96/100) and lowest on AI Readiness (55/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

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

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

Ownership

CucumberOrganization
1,008 followers141 public repossince Jul 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemscucumber11.1.1-20163 days ago

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
22.8/36Commit cadence — 33/52 weeks with commits
18/18Commit volume — 141 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year141
human_commit_share0.51
days_since_last_push1
active_weeks_last_year33
How it's scored
27/27Ships releases — 18 releases published
36/36Release recency — latest release 63 days ago
19.8/27Release cadence — a release every ~98.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count18
latest_release_tagv11.1.1
releases_from_tagsno
days_since_latest_release63
mean_days_between_releases98.2
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?

96Exceptional · 17% of overall
How it's scored
60/60Stars — 5,215 stars
25/25Forks — 1,118 forks
13/15Watchers — 220 watchers
Inputs used
forks1,118
stars5,215
watchers220
growth_stateorganic
growth_factor_pct100

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
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_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, github.com, opencollective.com
has_pull_request_templateyes
How it's scored
80/80Total downloads — 103,177,086 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescucumber
dependents—
ecosystemsrubygems
total_downloads103,177,086
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?

77Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.9/22.5Commit distribution — top contributor authored 43% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 51 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled98
top_contributor_share0.428
How it's scored
40.8/42Issue resolution — 97% of issues closed
22.8/30PR acceptance — 814/1,071 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 5/30 approved changesets -- score normalized to 1
Inputs used
merged_prs814
open_issues23
closed_issues798
prs_merged_7d0
prs_decided_7d0
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio0.972
closed_unmerged_prs257
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 backing — organization-owned
0/20Verified domain
21.6/25Owner reach — 1,008 followers of cucumber
25/25Track record — 141 public repos, account ~16 yr old
Inputs used
followers1,008
owner_typeOrganization
is_verifiedno
owner_logincucumber
public_repos141
account_age_days5,901

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 63 days ago
20/20Version history — 201 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescucumber
ecosystemsrubygems
any_deprecatedno
min_days_since_publish63

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 13 out of 13 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 site — https://cucumber.io
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicscucumber, ruby, polyglot-release, tidelift
has_wikino
homepagehttps://cucumber.io
docs_sitehttps://cucumber.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

79Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 5/30 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 51 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.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.

55Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
33.5/40Legible commit history — 32 of 51 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.627
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 49 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0.49
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/349 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes30,542
source_files_sampled349
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
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

5,215GitHub stars
98contributors
141commits, last 12 months
1days since last push
18releases
2bus factor
23open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-12: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 5215 stars today.
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 5,211 ★ / 1,118 ⇿
5,211Stars
1,118Forks
18Releases

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.

Star history is shown as collected on 2026-07-12. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01,0002,0003,0004,0005,0006,0005,2111,118522009-092018-022026-07
Major 4Minor 6Patch 7

Each point covers 16 days.

OpenSSF Scorecard 7.9 / 10
7.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-08-28 06:06 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/30 approved changesets -- score normalized to 1
10Contributorsproject has 51 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
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 22

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

RegistryPackageVersionRelation
RubyGemsbase64—indirect
RubyGemsbuilder—indirect
RubyGemscucumber-ci-environment—indirect
RubyGemscucumber-compatibility-kit—indirect
RubyGemscucumber-core—indirect
RubyGemscucumber-cucumber-expressions—indirect
RubyGemscucumber-html-formatter—indirect
RubyGemscucumber-query—indirect
RubyGemsdiff-lcs—indirect
RubyGemslogger—indirect
RubyGemsmini_mime—indirect
RubyGemsmulti_test—indirect
RubyGemsnokogiri—indirect
RubyGemsrake—indirect
RubyGemsrspec—indirect
RubyGemsrubocop—indirect
RubyGemsrubocop-packaging—indirect
RubyGemsrubocop-rake—indirect
RubyGemsrubocop-rspec—indirect
RubyGemssimplecov—indirect
RubyGemssys-uname—indirect
RubyGemswebrick—indirect
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 — RubyGems.