Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 19:07 UTC

launchdarkly / rust-server-sdk

LaunchDarkly Server-Side SDK for Rust

RustCustom license★ 18 stars⑂ 22 forkssince Nov 2020View on GitHub ↗
KindLibraryNetwork servicehow this is determined

launchdarkly/rust-server-sdk holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (86/100) and lowest on Engineering Quality (51/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

LaunchDarklyOrganization · verified domain
328 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 publishTags
crates.iolaunchdarkly-server-sdk3.2.0141,4083332 days agofeature-flagsfeature-toggleslaunchdarklylaunchdarkly-sdk

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
15.2/36Commit cadence — 22/52 weeks with commits
15.6/18Commit volume — 54 commits in the last year
10/10OpenSSF Scorecard: Maintained — 19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year54
human_commit_share0.66
days_since_last_push4
active_weeks_last_year22

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 32 releases published
36/36Release recency — latest release 32 days ago
27/27Release cadence — a release every ~26.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count32
latest_release_tag3.2.0
releases_from_tagsno
days_since_latest_release32
mean_days_between_releases26.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?

62Moderate · 17% of overall
How it's scored
20/60Stars — 18 stars
11/25Forks — 22 forks
8.4/15Watchers — 34 watchers
Inputs used
forks22
stars18
watchers34
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
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_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
68.7/80Monthly downloads — 141,408 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageslaunchdarkly-server-sdk
dependents—
ecosystemscrates
total_downloads5,347,316
monthly_downloads141,408
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
9/54Bus factor — 1 contributor(s) cover half of all commits
9.3/22.5Commit distribution — top contributor authored 59% of commits
13.5/13.5Contributor breadth — 10 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.587
How it's scored
35.8/42Issue resolution — 85% of issues closed
25.9/30PR acceptance — 139/161 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
13.5/15OpenSSF Scorecard: Code-Review — Found 18/19 approved changesets -- score normalized to 9
Inputs used
merged_prs139
open_issues5
closed_issues29
prs_merged_7d0
prs_decided_7d0
prs_merged_30d9
prs_decided_30d9
issue_closed_ratio0.853
closed_unmerged_prs22
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
20/20Verified domain
18.1/25Owner reach — 328 followers of launchdarkly
25/25Track record — 317 public repos, account ~12 yr old
Inputs used
followers328
owner_typeOrganization
is_verifiedyes
owner_loginlaunchdarkly
public_repos317
account_age_days4,456

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

51Moderate · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 28 out of 29 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 site — https://docs.launchdarkly.com/sdk/server-side/rust
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicslaunchdarkly, launchdarkly-sdk, feature-flags, feature-toggles, rust, sdk, managed-by-terraform
has_wikino
homepagehttps://docs.launchdarkly.com/sdk/server-side/rust
docs_sitehttps://docs.launchdarkly.com/sdk/server-side/rust
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

61Moderate · 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.2/2.5CI-Tests — 28 out of 29 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6.8/7.5Code-Review — Found 18/19 approved changesets -- score normalized to 9
2.5/2.5Contributors — project has 5 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 19 commit(s) and 2 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_aggregate6.1
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.

54Moderate · 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 — 64 of 66 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.97
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice — 6 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.06
toolchain_manifestsCargo.toml, contract-tests/Cargo.toml, launchdarkly-server-sdk/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
52.9/55Manageable file sizes — 2/52 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes94,219
source_files_sampled52
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

18GitHub stars
10contributors
54commits, last 12 months
4days since last push
32releases
1bus factor
5open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2025-10-17: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 18 stars today.
  • Could not fetch crates package 'contract-tests' from its registry
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 18 ★ / 22 ⇿
18Stars
22Forks
29Releases

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.

Star history is shown as collected on 2025-10-17. 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.

048121620181822022-012024-042026-07
Major 3Minor 8Patch 15

Each point covers 5 days.

OpenSSF Scorecard 6.1 / 10
6.1aggregate

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-09-12 19:06 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
9Code-ReviewFound 18/19 approved changesets -- score normalized to 9
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained19 commit(s) and 2 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 40
RegistryPackageVersion constraintManifest
crates.ioactix0.13.0contract-tests/Cargo.toml
crates.ioactix-web4.2.1contract-tests/Cargo.toml
crates.ioenv_logger0.10.0contract-tests/Cargo.toml
crates.ioeventsource-client0.17.0contract-tests/Cargo.toml
crates.iolaunchdarkly-sdk-transport0.1.0contract-tests/Cargo.toml
crates.iolog0.4.14contract-tests/Cargo.toml
crates.iolaunchdarkly-server-sdk—contract-tests/Cargo.toml
crates.ioserde1.0.132contract-tests/Cargo.toml
crates.ioserde_json1.0.73contract-tests/Cargo.toml
crates.iofutures0.3.12contract-tests/Cargo.toml
crates.iohyper-util0.1contract-tests/Cargo.toml
crates.iohyper-rustls0.27contract-tests/Cargo.toml
crates.iohyper-tls0.6.0contract-tests/Cargo.toml
crates.ioreqwest0.12.4contract-tests/Cargo.toml
crates.ioasync-mutex1.4.0contract-tests/Cargo.toml
crates.iochrono0.4.19launchdarkly-server-sdk/Cargo.toml
crates.iocrossbeam-channel0.5.1launchdarkly-server-sdk/Cargo.toml
crates.iodata-encoding2.3.2launchdarkly-server-sdk/Cargo.toml
crates.ioeventsource-client0.18.0launchdarkly-server-sdk/Cargo.toml
crates.iolaunchdarkly-sdk-transport0.1.0launchdarkly-server-sdk/Cargo.toml
crates.iofutures0.3.12launchdarkly-server-sdk/Cargo.toml
crates.iolog0.4.14launchdarkly-server-sdk/Cargo.toml
crates.iolru0.16.3launchdarkly-server-sdk/Cargo.toml
crates.iolaunchdarkly-server-sdk-evaluation2.2.1launchdarkly-server-sdk/Cargo.toml
crates.ioserde1.0.132launchdarkly-server-sdk/Cargo.toml
crates.ioserde_json1.0.73launchdarkly-server-sdk/Cargo.toml
crates.iothiserror2.0launchdarkly-server-sdk/Cargo.toml
crates.iotokio1.17.0launchdarkly-server-sdk/Cargo.toml
crates.ioparking_lot0.12.0launchdarkly-server-sdk/Cargo.toml
crates.iotokio-stream0.1.8launchdarkly-server-sdk/Cargo.toml
crates.iomoka0.12.1launchdarkly-server-sdk/Cargo.toml
crates.iouuid1.2.2launchdarkly-server-sdk/Cargo.toml
crates.iohttp1.0launchdarkly-server-sdk/Cargo.toml
crates.iobytes1.11launchdarkly-server-sdk/Cargo.toml
crates.iopercent-encoding2.3launchdarkly-server-sdk/Cargo.toml
crates.iobitflags2.4launchdarkly-server-sdk/Cargo.toml
crates.iorand0.9launchdarkly-server-sdk/Cargo.toml
crates.ioflate21.0.35launchdarkly-server-sdk/Cargo.toml
crates.ioaws-lc-rs1.14.1launchdarkly-server-sdk/Cargo.toml
crates.ioopenssl0.10.75launchdarkly-server-sdk/Cargo.toml
All dependencies 39

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

RegistryPackageVersionRelation
crates.ioactix—direct
crates.ioactix-web—direct
crates.ioasync-mutex—direct
crates.ioaws-lc-rs—direct
crates.iobitflags—direct
crates.iobytes—direct
crates.iochrono—direct
crates.iocrossbeam-channel—direct
crates.iodata-encoding—direct
crates.ioenv_logger—direct
crates.ioeventsource-client—direct
crates.ioflate2—direct
crates.iofutures—direct
crates.iohttp—direct
crates.iohyper-rustls—direct
crates.iohyper-tls—direct
crates.iohyper-util—direct
crates.iolaunchdarkly-sdk-transport—direct
crates.iolaunchdarkly-server-sdk-evaluation—direct
crates.iolog—direct
crates.iolru—direct
crates.iomoka—direct
crates.ioopenssl—direct
crates.ioparking_lot—direct
crates.iopercent-encoding—direct
crates.iorand—direct
crates.ioreqwest—direct
crates.ioserde—direct
crates.ioserde_json—direct
crates.iothiserror—direct
crates.iotokio—direct
crates.iotokio-stream—direct
crates.iouuid—direct
crates.ioassert-json-diff—indirect
crates.ioasync-std—indirect
crates.iomaplit—indirect
crates.iomockito—indirect
crates.iotest-case—indirect
crates.iotesting_logger—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 — crates.io.