Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 22:40 UTC

launchdarkly / ruby-server-sdk

LaunchDarkly Server-side SDK for Ruby

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

launchdarkly/ruby-server-sdk holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Vitality (93/100) and lowest on AI Readiness (63/100). It was last updated today. 3 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 83 is calibrated to 96 on the published index scale (record calibration 2026-08-02).

Ownership

LaunchDarklyOrganization · verified domain
336 followers317 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.19.0-1074 days ago

Metrics by category

Vitality

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

93Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
23.5/36Commit cadence — 34/52 weeks with commits
18/18Commit volume — 110 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_year110
human_commit_share0.62
days_since_last_push0
active_weeks_last_year34

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~15.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag8.19.0
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases15.1
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?

70Good · 17% of overall
How it's scored
28/60Stars — 54 stars
14.6/25Forks — 57 forks
9.1/15Watchers — 45 watchers
Inputs used
forks57
stars54
watchers45
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license 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.7/80Total downloads — 30,126,502 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageslaunchdarkly-server-sdk
dependents—
ecosystemsrubygems
total_downloads30,126,502
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?

89Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
16.6/22.5Commit distribution — top contributor authored 26% of commits
13.5/13.5Contributor breadth — 41 contributors
10/10OpenSSF Scorecard: Contributors — project has 18 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled41
top_contributor_share0.261
How it's scored
41/42Issue resolution — 98% of issues closed
27/30PR acceptance — 337/375 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs337
open_issues2
closed_issues83
prs_merged_7d2
prs_decided_7d2
prs_merged_30d13
prs_decided_30d15
issue_closed_ratio0.976
closed_unmerged_prs38
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
18.2/25Owner reach — 336 followers of launchdarkly
25/25Track record — 317 public repos, account ~12 yr old
Inputs used
followers336
owner_typeOrganization
is_verifiedyes
owner_loginlaunchdarkly
public_repos317
account_age_days4,493

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 4 days ago
20/20Version history — 107 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslaunchdarkly-server-sdk
ecosystemsrubygems
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 28 out of 28 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://docs.launchdarkly.com/sdk/server-side/ruby
10/10Repository description
10/10Topics — 8 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-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 28 out of 28 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 18 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.2/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
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages26
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. 26 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 instructions — no 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 history — 61 of 62 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 bootstrap — Makefile, docs/Makefile
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice — 13 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 18 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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.13
toolchain_manifests—
dependency_bot_commit_share0.18
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/192 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes37,054
source_files_sampled192
oversized_source_files0

Key facts

54GitHub stars
41contributors
110commits, last 12 months
0days since last push
100releases
3bus 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 ★ / 57 ⇿
0Stars
57Forks
96Releases

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.

01020304050605522015-042020-122026-09
Major 5Minor 32Patch 59

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-10-19 22:40 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests28 out of 28 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
RubyGemsld-eventsource—Gemfile
RubyGemslaunchdarkly-server-sdk—contract-tests/Gemfile
RubyGemshttp>= 5.1contract-tests/Gemfile
RubyGemsjson—contract-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 27

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

RegistryPackageVersionRelation
RubyGemsaws-sdk-dynamodb—direct
RubyGemsconnection_pool—direct
RubyGemsdiplomat—direct
RubyGemshttp—direct
RubyGemsjson—direct
RubyGemslaunchdarkly-server-sdk—direct
RubyGemsld-eventsource—direct
RubyGemsld-eventsource3.0.1direct
RubyGemspuma—direct
RubyGemsrackup—direct
RubyGemsredis—direct
RubyGemssinatra—direct
RubyGemsbenchmark—indirect
RubyGemsbigdecimal—indirect
RubyGemsconcurrent-ruby—indirect
RubyGemslisten—indirect
RubyGemsobserver—indirect
RubyGemsopenssl—indirect
RubyGemsrexml—indirect
RubyGemsrspec—indirect
RubyGemsrspec_junit_formatter—indirect
RubyGemsrubocop—indirect
RubyGemsrubocop-performance—indirect
RubyGemssemantic—indirect
RubyGemssimplecov—indirect
RubyGemstimecop—indirect
RubyGemswebrick—indirect
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. 26 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 statistics — RubyGems.