Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-20 21:56 UTC

launchdarkly / ruby-server-sdk

LaunchDarkly Server-side SDK for Ruby

RubyCustom license★ 53 stars⑂ 55 forkssince Sep 2014View on GitHub ↗
KindLibraryCommand-line toolNetwork servicehow this is determined

launchdarkly/ruby-server-sdk holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Vitality (89/100) and lowest on AI Readiness (63/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

LaunchDarklyOrganization
323 followers316 public repossince Jul 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemslaunchdarkly-server-sdk8.15.0-910 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 recencylast push 0 days ago
19.4/36Commit cadence28/52 weeks with commits
16.9/18Commit volume76 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year76
human_commit_share0.61
days_since_last_push0
active_weeks_last_year28

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~34.9 days
10/10OpenSSF Scorecard: Signed-Releases1 out of the last 1 releases have a total of 1 signed artifacts.
Inputs used
releases_count100
latest_release_tag8.15.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases34.9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

70Good · 17% of overall
How it's scored
27.8/60Stars53 stars
14.4/25Forks55 forks
9.1/15Watchers45 watchers
Inputs used
forks55
stars53
watchers45
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
18/18CONTRIBUTING guide
0/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_conductno
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
77.5/80Total downloads28,791,438 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageslaunchdarkly-server-sdk
dependents
ecosystemsrubygems
total_downloads28,791,438
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?

82Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
16.4/22.5Commit distributiontop contributor authored 27% of commits
13.5/13.5Contributor breadth38 contributors
10/10OpenSSF Scorecard: Contributorsproject has 18 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled38
top_contributor_share0.269
How it's scored
41/42Issue resolution98% of issues closed
27.1/30PR acceptance304/337 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 8/9 approved changesets -- score normalized to 8
Inputs used
merged_prs304
open_issues2
closed_issues82
prs_merged_7d5
prs_decided_7d7
prs_merged_30d5
prs_decided_30d8
issue_closed_ratio0.976
closed_unmerged_prs33
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
18/25Owner reach323 followers of launchdarkly
25/25Track record316 public repos, account ~12 yr old
Inputs used
followers323
owner_typeOrganization
is_verified
owner_loginlaunchdarkly
public_repos316
account_age_days4,433
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 history91 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageslaunchdarkly-server-sdk
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

85Excellent · 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
18/20OpenSSF Scorecard: CI-Tests28 out of 29 merged PRs checked by a CI test -- score normalized to 9
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://docs.launchdarkly.com/sdk/server-side/ruby
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicsruby, launchdarkly, rails, feature-flags, feature-toggles, sdk, launchdarkly-sdk, managed-by-terraform
has_wikino
homepagehttps://docs.launchdarkly.com/sdk/server-side/ruby
docs_sitehttps://docs.launchdarkly.com/sdk/server-side/ruby
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

76Good · 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
2.2/2.5CI-Tests28 out of 29 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 8/9 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 18 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 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
1.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0/5SASTSAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policysecurity policy file detected
7.5/7.5Signed-Releases1 out of the last 1 releases have a total of 1 signed artifacts.
0/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
Excluded from scoring (no data or not applicable): Packaging. 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_packages1
unassessed_packages25
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 1 resolved dependencies against OSV. 25 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.

63Moderate · 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://docs.launchdarkly.com/llms.txt)
40/40Legible commit history60 of 61 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.launchdarkly.com/llms.txt
legible_history_share0.984
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile, docs/Makefile
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice9 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance18 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.09
toolchain_manifests
dependency_bot_commit_share0.18
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/185 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes33,807
source_files_sampled185
oversized_source_files0

Key facts

53GitHub stars
38contributors
76commits, last 12 months
0days since last push
100releases
2bus factor
2open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 55 ⇿
0Stars
55Forks
99Releases

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.

01020304050605322015-042020-112026-07
Major 6Minor 30Patch 63

Each point covers 11 days.

OpenSSF Scorecard 7.0 / 10
7.0aggregate

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

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests28 out of 29 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 8/9 approved changesets -- score normalized to 8
10Contributorsproject has 18 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 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
10Signed-Releases1 out of the last 1 releases have a total of 1 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
RubyGemslaunchdarkly-server-sdkcontract-tests/Gemfile
RubyGemshttp>= 5.1contract-tests/Gemfile
RubyGemsjsoncontract-tests/Gemfile
RubyGemspuma~> 8.0contract-tests/Gemfile
RubyGemsrackup~> 2.2contract-tests/Gemfile
RubyGemssinatra>= 4.1contract-tests/Gemfile
RubyGemsconnection_pool~> 3.0contract-tests/Gemfile
RubyGemsredis~> 5.3contract-tests/Gemfile
RubyGemsdiplomat~> 2.6contract-tests/Gemfile
RubyGemsaws-sdk-dynamodb~> 1.127contract-tests/Gemfile
All dependencies 26

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

RegistryPackageVersionRelation
RubyGemsaws-sdk-dynamodbdirect
RubyGemsconnection_pooldirect
RubyGemsdiplomatdirect
RubyGemshttpdirect
RubyGemsjsondirect
RubyGemslaunchdarkly-server-sdkdirect
RubyGemspumadirect
RubyGemsrackupdirect
RubyGemsredisdirect
RubyGemssinatradirect
RubyGemsbenchmarkindirect
RubyGemsbigdecimalindirect
RubyGemsconcurrent-rubyindirect
RubyGemsld-eventsource2.6.0indirect
RubyGemslistenindirect
RubyGemsobserverindirect
RubyGemsopensslindirect
RubyGemsrexmlindirect
RubyGemsrspecindirect
RubyGemsrspec_junit_formatterindirect
RubyGemsrubocopindirect
RubyGemsrubocop-performanceindirect
RubyGemssemanticindirect
RubyGemssimplecovindirect
RubyGemstimecopindirect
RubyGemswebrickindirect
Dependency advisories 0

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

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

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