Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-23 17:42 UTC

launchdarkly / api-client-python

LaunchDarkly API Client for Python

PythonCustom license★ 5 stars⑂ 5 forkssince Sep 2017View on GitHub ↗

launchdarkly/api-client-python holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (78/100) and lowest on Security (14/100). It was last updated today. A single contributor accounts for most of its recent work.

62
overall / 100
Moderate

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.

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

Ownership

LaunchDarklyOrganization · verified domain
337 followers318 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
PyPIlaunchdarkly_api25.0.0470,959700 days agoopenapiopenapi-generatorlaunchdarkly-rest-api

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
4.8/36Commit cadence — 7/52 weeks with commits
10.6/18Commit volume — 14 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year14
human_commit_share1
days_since_last_push0
active_weeks_last_year7
How it's scored
27/27Ships releases — 29 releases published
36/36Release recency — latest release 81 days ago
19.8/27Release cadence — a release every ~54 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count29
latest_release_tagv24.0.0
releases_from_tagsno
days_since_latest_release81
mean_days_between_releases54

Community & Adoption

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

48Weak · 17% of overall
How it's scored
9.8/60Stars — 5 stars
5/25Forks — 5 forks
8.7/15Watchers — 37 watchers
Inputs used
forks5
stars5
watchers37
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
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
75.6/80Monthly downloads — 470,959 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageslaunchdarkly_api
dependents—
ecosystemspypi
total_downloads—
monthly_downloads470,959
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?

72Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.9/22.5Commit distribution — top contributor authored 65% of commits
5.4/13.5Contributor breadth — 4 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.647
How it's scored
39.5/42Issue resolution — 94% of issues closed
22.5/30PR acceptance — 3/4 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs3
open_issues1
closed_issues16
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.941
closed_unmerged_prs1
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.2/25Owner reach — 337 followers of launchdarkly
25/25Track record — 318 public repos, account ~12 yr old
Inputs used
followers337
owner_typeOrganization
is_verifiedyes
owner_loginlaunchdarkly
public_repos318
account_age_days4,497

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 — 70 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslaunchdarkly_api
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.pylint]), setup.cfg ([flake8]), tox.ini
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicslaunchdarkly, launchdarkly-api, api-client, open-api, feature-flags, feature-toggles, python, managed-by-terraform
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

14Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestspyproject.toml, requirements.txt, setup.cfg, setup.py
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: urllib3 2.6.3 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 165 days ago
Inputs used
sourceosv
advisories32
affected_packages4
assessed_packages38
unassessed_packages10
affected_by_severityhigh 2, moderate 2
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 38 resolved dependencies against OSV. 10 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.

43Weak · 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)
1.6/40Legible commit history — 3 of 100 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.03
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.pylint]), setup.cfg ([flake8]), tox.ini
11/11Static type checking — launchdarkly_api/py.typed
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configslaunchdarkly_api/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (launchdarkly_api/py.typed)
52.8/55Manageable file sizes — 59/1,454 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes804,289
source_files_sampled1,454
oversized_source_files59

Key facts

5GitHub stars
4contributors
14commits, last 12 months
0days since last push
29releases
1bus factor
1open 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_api@25.0.0; advisories assessed against the repository dependency graph instead
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 5 ⇿
0Stars
5Forks
9Releases

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.

12345512019-082021-042022-12
Major 6Minor 1Patch 2

Each point covers 4 days.

Direct dependencies 4
RegistryPackageVersion constraintManifest
PyPIurllib3(>=2.1.0,<3.0.0)pyproject.toml
PyPIpython-dateutil(>=2.8.2)pyproject.toml
PyPIpydantic(>=2)pyproject.toml
PyPItyping-extensions(>=4.7.1)pyproject.toml
All dependencies 48

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

RegistryPackageVersionRelation
PyPIpydantic—direct
PyPIpydantic2.13.4direct
PyPIpython-dateutil—direct
PyPIpython-dateutil2.9.0.post0direct
PyPItyping-extensions—direct
PyPItyping-extensions4.16.0direct
PyPIurllib3—direct
PyPIurllib32.6.3direct
PyPIannotated-types0.7.0indirect
PyPIast-serialize0.6.0indirect
PyPIcachetools6.2.6indirect
PyPIchardet5.2.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.10.7indirect
PyPIdistlib0.4.3indirect
PyPIexceptiongroup1.3.1indirect
PyPIfilelock3.19.1indirect
PyPIflake8—indirect
PyPIflake87.3.0indirect
PyPIiniconfig2.1.0indirect
PyPIlibrt0.13.0indirect
PyPImccabe0.7.0indirect
PyPImypy—indirect
PyPImypy1.19.1indirect
PyPImypy-extensions1.1.0indirect
PyPIpackaging26.2indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.4.0indirect
PyPIpluggy1.6.0indirect
PyPIpycodestyle2.14.0indirect
PyPIpydantic-core2.46.4indirect
PyPIpyflakes3.4.0indirect
PyPIpygments2.20.0indirect
PyPIpyproject-api1.9.1indirect
PyPIpytest—indirect
PyPIpytest8.4.2indirect
PyPIpytest-cov—indirect
PyPIpytest-cov7.1.0indirect
PyPIpython-discovery1.5.1indirect
PyPIsix1.17.0indirect
PyPItomli2.4.1indirect
PyPItomli-w1.2.0indirect
PyPItox—indirect
PyPItox4.30.3indirect
PyPItypes-python-dateutil—indirect
PyPItypes-python-dateutil2.9.0.20260124indirect
PyPItyping-inspection0.4.2indirect
PyPIvirtualenv21.7.1indirect
Dependency advisories 4

This repository publishes no package the index resolves, so its own dependency graph was assessed — 38 packages, which also include development and test pins that never ship: 4 carry known advisories, of which 1 are direct. 10 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
urllib32.6.3directhigh102.8.0
virtualenv21.7.1indirecthigh1621.14.9
filelock3.19.1indirectmoderate43.20.3
pytest8.4.2indirectmoderate29.0.3

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.