Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 11:29 UTC

rudderlabs / rudder-sdk-ruby

Ruby SDK for RudderStack - Open-source, warehouse-first Customer Data Pipeline and Segment-alternative. Collects and routes clickstream data and builds your customer data lake on your data warehouse.

RubyCustom license★ 2 stars⑂ 0 forkssince Dec 2019View on GitHub ↗

rudderlabs/rudder-sdk-ruby holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (88/100) and lowest on Community & Adoption (38/100). It was last updated today. 3 contributors account for most of its recent work.

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

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

Ownership

RudderStackOrganization
333 followers189 public repossince Jul 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsrudder-sdk-ruby3.2.1-140 days ago

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
4.8/36Commit cadence7/52 weeks with commits
9.7/18Commit volume11 commits in the last year
6/10OpenSSF Scorecard: Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year11
human_commit_share0.96
days_since_last_push0
active_weeks_last_year7
How it's scored
27/27Ships releases9 releases published
36/36Release recencylatest release 0 days ago
12.6/27Release cadencea release every ~153.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count9
latest_release_tagv3.2.1
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases153.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?

38Weak · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
61.8/80Total downloads888,462 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesrudder-sdk-ruby
dependents
ecosystemsrubygems
total_downloads888,462
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?

88Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
16.7/22.5Commit distributiontop contributor authored 26% of commits
13.5/13.5Contributor breadth58 contributors
10/10OpenSSF Scorecard: Contributorsproject has 27 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled58
top_contributor_share0.258
How it's scored
42/42Issue resolution100% of issues closed
24.2/30PR acceptance29/36 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 18/22 approved changesets -- score normalized to 8
Inputs used
merged_prs29
open_issues0
closed_issues3
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs7
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
18.1/25Owner reach333 followers of rudderlabs
25/25Track record189 public repos, account ~7 yr old
Inputs used
followers333
owner_typeOrganization
is_verified
owner_loginrudderlabs
public_repos189
account_age_days2,576
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 0 days ago
20/20Version history14 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesrudder-sdk-ruby
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests13 out of 23 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://rudderstack.com/
10/10Repository description
10/10Topics1 topics
10/10Wiki
Inputs used
topicsruby
has_wikiyes
homepagehttps://rudderstack.com/
docs_sitehttps://rudderstack.com/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

82Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.2/2.5CI-Tests13 out of 23 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6/7.5Code-ReviewFound 18/22 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 27 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
4.5/7.5Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
2/5SASTSAST tool is not run on all commits -- score normalized to 4
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.8
Excluded from scoring (no data or not applicable): 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
advisories1
affected_packages1
assessed_packages1
unassessed_packages9
affected_by_severityhigh 1
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 1 resolved dependencies against OSV. 9 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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
28.9/40Legible commit history52 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.542
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 practice1 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
10/10OpenSSF Scorecard: Pinned-Dependenciesall 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
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/34 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes16,674
source_files_sampled34
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 examplesexample
Inputs used
example_dirsexample
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

2GitHub stars
58contributors
11commits, last 12 months
0days since last push
9releases
3bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 7.8 / 10
7.8aggregate

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-22 11:29 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests13 out of 23 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 18/22 approved changesets -- score normalized to 8
10Contributorsproject has 27 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
4SASTSAST tool is not run on all commits -- score normalized to 4
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
RubyGemsdebugGemfile
RubyGemssolargraphGemfile
All dependencies 10

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

RegistryPackageVersionRelation
RubyGemsdebugdirect
RubyGemssolargraphdirect
RubyGemsactivesupportindirect
RubyGemscodecovindirect
RubyGemscommanderindirect
RubyGemsojindirect
RubyGemsrakeindirect
RubyGemsrspecindirect
RubyGemsrubocopindirect
RubyGemstzinfo1.2.1indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 9 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
tzinfo1.2.1indirecthigh11.2.10

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

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