Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-25 22:59 UTC

launchdarkly / openfeature-dotnet-server

An OpenFeature provider for the LaunchDarkly dotnet server SDK.

C#Custom license★ 7 stars⑂ 6 forkssince Sep 2022View on GitHub ↗

launchdarkly/openfeature-dotnet-server holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (71/100) and lowest on Engineering Quality (52/100). It was last updated today. A single contributor accounts for most of its recent work.

71
overall / 100
Good

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.

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

Ownership

LaunchDarklyOrganization · verified domain
324 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
NuGetLaunchDarkly.OpenFeature.ServerProvider2.3.0-150 days ago

Metrics by category

Vitality

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

70Good · 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
5/10OpenSSF Scorecard: Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year11
human_commit_share0.797
days_since_last_push0
active_weeks_last_year7
How it's scored
27/27Ships releases15 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~100.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count15
latest_release_tag2.3.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases100.8
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?

56Moderate · 17% of overall
How it's scored
12.6/60Stars7 stars
5.8/25Forks6 forks
8/15Watchers29 watchers
Inputs used
forks6
stars7
watchers29
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_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
65.6/80Total downloads2,048,905 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesLaunchDarkly.OpenFeature.ServerProvider
dependents
ecosystemsnuget
total_downloads2,048,905
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?

71Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.6/22.5Commit distributiontop contributor authored 66% of commits
12.2/13.5Contributor breadth9 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.66
How it's scored
14/42Issue resolution33% of issues closed
28.4/30PR acceptance55/58 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 16/18 approved changesets -- score normalized to 8
Inputs used
merged_prs55
open_issues2
closed_issues1
prs_merged_7d3
prs_decided_7d3
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.333
closed_unmerged_prs3
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 backingorganization-owned
20/20Verified domain
18.1/25Owner reach324 followers of launchdarkly
25/25Track record316 public repos, account ~12 yr old
Inputs used
followers324
owner_typeOrganization
is_verifiedyes
owner_loginlaunchdarkly
public_repos316
account_age_days4,438

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on nuget
35/35Publish recencylatest publish 0 days ago
20/20Version history15 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesLaunchDarkly.OpenFeature.ServerProvider
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests10 out of 26 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicslaunchdarkly, feature-flags, feature-toggles, launchdarkly-sdk, open-feature, sdk, managed-by-terraform
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

62Moderate · 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
0.8/2.5CI-Tests10 out of 26 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6/7.5Code-ReviewFound 16/18 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
3.8/7.5Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
0/5Packagingno data
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0/5SASTSAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.3
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 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_packages9
unassessed_packages2
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 9 resolved dependencies against OSV. 2 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.

64Moderate · 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 history43 of 55 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.782
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapsrc/LaunchDarkly.OpenFeature.ServerProvider/LaunchDarkly.OpenFeature.ServerProvider.csproj, test/LaunchDarkly.OpenFeature.ServerProvider.Tests/LaunchDarkly.OpenFeature.ServerProvider.Tests.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice6 of the last 69 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.087
toolchain_manifestssrc/LaunchDarkly.OpenFeature.ServerProvider/LaunchDarkly.OpenFeature.ServerProvider.csproj, test/LaunchDarkly.OpenFeature.ServerProvider.Tests/LaunchDarkly.OpenFeature.ServerProvider.Tests.csproj
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/16 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes18,392
source_files_sampled16
oversized_source_files0

Key facts

7GitHub stars
9contributors
11commits, last 12 months
0days since last push
15releases
1bus factor
2open issues
package ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 6 ⇿
0Stars
6Forks
10Releases

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.

123456612022-102024-032025-07
Major 2Minor 7Patch 1

Each point covers 3 days.

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-25 22:58 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
3CI-Tests10 out of 26 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 16/18 approved changesets -- score normalized to 8
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
5Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
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 2
RegistryPackageVersion constraintManifest
NuGetLaunchDarkly.ServerSdk[8.1.0,9.0)src/LaunchDarkly.OpenFeature.ServerProvider/LaunchDarkly.OpenFeature.ServerProvider.csproj
NuGetOpenFeature[2.2.0, 3.0.0)src/LaunchDarkly.OpenFeature.ServerProvider/LaunchDarkly.OpenFeature.ServerProvider.csproj
All dependencies 11

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

RegistryPackageVersionRelation
NuGetLaunchDarkly.ServerSdkdirect
NuGetLaunchDarkly.ServerSdk8.5.1direct
NuGetOpenFeaturedirect
NuGetOpenFeature2.2.0direct
NuGetcoverlet.collector3.1.0indirect
NuGetLaunchDarkly.TestHelpers2.0.0indirect
NuGetMicrosoft.NET.Test.Sdk16.11.0indirect
NuGetMicrosoft.TestPlatform.ObjectModel16.6.1indirect
NuGetMoq4.8.1indirect
NuGetxunit2.4.1indirect
NuGetxunit.runner.visualstudio2.4.3indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 9 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 2 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 statisticsNuGet.