Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 21:23 UTC

launchdarkly / python-server-sdk

LaunchDarkly Server-side SDK for Python

PythonCustom license★ 44 stars⑂ 50 forkssince Aug 2014View on GitHub ↗

launchdarkly/python-server-sdk holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Vitality (96/100) and lowest on Community & Adoption (70/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 84 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
PyPIlaunchdarkly-server-sdk9.18.39,377,739810 days ago

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
29.1/36Commit cadence — 42/52 weeks with commits
18/18Commit volume — 151 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_year151
human_commit_share0.68
days_since_last_push0
active_weeks_last_year42

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~34.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag9.18.3
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases34.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?

70Good · 17% of overall
How it's scored
26.5/60Stars — 44 stars
14.1/25Forks — 50 forks
9.3/15Watchers — 48 watchers
Inputs used
forks50
stars44
watchers48
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_servicesgithub.com, readthedocs.org, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 9,377,739 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageslaunchdarkly-server-sdk
dependents—
ecosystemspypi
total_downloads—
monthly_downloads9,377,739
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?

90Excellent · 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 — 34 contributors
10/10OpenSSF Scorecard: Contributors — project has 11 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled34
top_contributor_share0.264
How it's scored
38.8/42Issue resolution — 92% of issues closed
28/30PR acceptance — 404/433 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs404
open_issues7
closed_issues85
prs_merged_7d2
prs_decided_7d2
prs_merged_30d7
prs_decided_30d9
issue_closed_ratio0.924
closed_unmerged_prs29
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
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,494

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — contract-tests/setup.cfg ([pycodestyle]), pyproject.toml ([tool.isort]), setup.cfg ([pycodestyle])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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/python
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicslaunchdarkly, python, feature-flags, feature-toggles, sdk, launchdarkly-sdk, managed-by-terraform
has_wikino
homepagehttps://docs.launchdarkly.com/sdk/server-side/python
docs_sitehttps://docs.launchdarkly.com/sdk/server-side/python
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

78Good · 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 — 30 out of 30 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 11 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
5/5Packaging — packaging workflow detected
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
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_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.2
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 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_packages3
unassessed_packages29
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 3 resolved dependencies against OSV. 29 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.

73Good · 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 — 67 of 68 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.985
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — contract-tests/setup.cfg ([pycodestyle]), pyproject.toml ([tool.isort]), setup.cfg ([pycodestyle])
11/11Static type checking — ldclient/py.typed
0/10Reproducible environment
10/10Demonstrated agent practice — 6 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 22 of the last 100 commits are automated dependency updates
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configsldclient/py.typed
agent_commit_share0.06
toolchain_manifests—
dependency_bot_commit_share0.22
How it's scored
27/45Type-checkable code — Python with type-check config (ldclient/py.typed)
54.8/55Manageable file sizes — 1/240 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes81,344
source_files_sampled240
oversized_source_files1

Key facts

44GitHub stars
34contributors
151commits, last 12 months
0days since last push
100releases
3bus factor
7open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:launchdarkly-server-sdk@9.18.3; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 50 ⇿
0Stars
50Forks
98Releases

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.

010203040505032014-092020-092026-10
Major 3Minor 40Patch 55

Each point covers 12 days.

OpenSSF Scorecard 7.2 / 10
7.2aggregate

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

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 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 11 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
10Packagingpackaging workflow detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
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 6
RegistryPackageVersion constraintManifest
PyPIcertifi>=2026.10.19pyproject.toml
PyPIexpiringdict>=1.1.4pyproject.toml
PyPIpyRFC3339>=1.0pyproject.toml
PyPIsemver>=2.10.2pyproject.toml
PyPIurllib3>=1.26.0,<3pyproject.toml
PyPIlaunchdarkly-eventsource>=1.7.2,<2.0.0pyproject.toml
All dependencies 32

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

RegistryPackageVersionRelation
PyPIcertifi—direct
PyPIexpiringdict—direct
PyPIlaunchdarkly-eventsource—direct
PyPIpyrfc3339—direct
PyPIsemver—direct
PyPIurllib3—direct
PyPIaioboto3—indirect
PyPIaiohttp—indirect
PyPIboto3—indirect
PyPIcoverage—indirect
PyPIflask—indirect
PyPIisort—indirect
PyPIjinja23.1.6indirect
PyPIjsonpickle—indirect
PyPImock—indirect
PyPImypy2.3.0indirect
PyPIpycodestyle—indirect
PyPIpytest—indirect
PyPIpytest-asyncio—indirect
PyPIpytest-cov—indirect
PyPIpytest-mypy1.0.1indirect
PyPIpython-consul—indirect
PyPIpyyaml—indirect
PyPIredis—indirect
PyPIrequests—indirect
PyPIsphinx—indirect
PyPIsphinx-rtd-theme—indirect
PyPItypes-mock—indirect
PyPItypes-pyyaml—indirect
PyPItypes-redis—indirect
PyPItypes-setuptools—indirect
PyPIwatchdog—indirect
Dependency advisories 0

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