Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 21:05 UTC

lightgbm-org / LightGBM

A fast, distributed, high performance gradient boosting (GBT, GBDT, GBRT, GBM or MART) framework based on decision tree algorithms, used for ranking, classification and many other machine learning tasks.

C++ · Python · RMIT★ 18,770 stars⑂ 4,071 forkssince Aug 2016View on GitHub ↗

lightgbm-org/LightGBM holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (96/100) and lowest on Security (47/100). It was last updated 3 days ago. 2 contributors account for most of its recent work.

34
overall / 100
At Risk

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.

34
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 80 is calibrated to 94 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

lightgbm-orgOrganization
23 followers2 public repossince Mar 2026

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIlightgbm4.7.019,915,8173860 days ago

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
33.2/36Commit cadence — 48/52 weeks with commits
18/18Commit volume — 173 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year173
human_commit_share0.93
days_since_last_push3
active_weeks_last_year48
How it's scored
27/27Ships releases — 35 releases published
36/36Release recency — latest release 60 days ago
12.6/27Release cadence — a release every ~143.4 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count35
latest_release_tagv4.7.0
releases_from_tagsno
days_since_latest_release60
mean_days_between_releases143.4

Community & Adoption

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

95Exceptional · 17% of overall

Popularity & adoption

100Exceptional
How it's scored
60/60Stars — 18,770 stars
25/25Forks — 4,071 forks
14.6/15Watchers — 422 watchers
Inputs used
forks4,071
stars18,770
watchers422
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges17
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesci.appveyor.com, github.com, readthedocs.org, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 19,915,817 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageslightgbm
dependents—
ecosystemspypi
total_downloads—
monthly_downloads19,915,817
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
25.2/54Bus factor — 2 contributor(s) cover half of all commits
16.5/22.5Commit distribution — top contributor authored 27% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 39 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.267
How it's scored
36.9/42Issue resolution — 88% of issues closed
26.7/30PR acceptance — 3,250/3,649 decided PRs merged
7.8/13Newcomer PR acceptance — 6/10 first-time contributors' PRs merged in 30d
13.5/15OpenSSF Scorecard: Code-Review — Found 27/28 approved changesets -- score normalized to 9
Inputs used
merged_prs3,250
open_issues447
closed_issues3,242
prs_merged_7d2
prs_decided_7d2
prs_merged_30d19
prs_decided_30d23
issue_closed_ratio0.879
closed_unmerged_prs399
first_time_authors_30d9
first_time_prs_merged_30d6
first_time_prs_decided_30d10
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
9.9/25Owner reach — 23 followers of lightgbm-org
4.5/25Track record — 2 public repos, account ~0 yr old
Inputs used
followers23
owner_typeOrganization
is_verifiedno
owner_loginlightgbm-org
public_repos2
account_age_days193

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 60 days ago
20/20Version history — 38 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslightgbm
ecosystemspypi
any_deprecatedno
min_days_since_publish60

Engineering Quality

Are baseline engineering and documentation practices in place?

96Exceptional · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows — 15 workflow(s)
24/24Tests present
16/16Linter config — biome.json, python-package/pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 29 out of 29 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://lightgbm.readthedocs.io/en/latest/
10/10Repository description
10/10Topics — 13 topics
0/10Wiki
Inputs used
topicsgbdt, gbm, machine-learning, data-mining, distributed, lightgbm, gbrt, decision-trees, gradient-boosting, python, r, parallel, kaggle
has_wikino
homepagehttps://lightgbm.readthedocs.io/en/latest/
docs_sitehttps://lightgbm.readthedocs.io/en/latest/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 29 out of 29 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
6.8/7.5Code-Review — Found 27/28 approved changesets -- score normalized to 9
2.5/2.5Contributors — project has 39 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.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 12 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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
3/7.5Vulnerabilities — 6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.1
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier50
security_posture_after_multiplier36
security_posture_before_jurisdiction71
Excluded from scoring (no data or not applicable): Branch-Protection. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages3
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:lightgbm@4.7.0 runtime dependency closure — what installing the published package pulls in — 3 packages. 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.

75Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
38.4/40Legible commit history — 67 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.72
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — biome.json, python-package/pyproject.toml ([tool.ruff])
11/11Static type checking — python-package/lightgbm/py.typed
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 7 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_dockerfileyes
typed_languageyes
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configspython-package/lightgbm/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.07
How it's scored
45/45Type-checkable code — C++ (statically typed)
51.9/55Manageable file sizes — 12/216 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes211,642
source_files_sampled216
oversized_source_files12
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples, notebooks
Inputs used
example_dirsexamples, notebooks
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

18,770GitHub stars
99contributors
173commits, last 12 months
3days since last push
35releases
2bus factor
447open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 14 authors (cap 12)

More detail

Star and fork history 0 ★ / 4,071 ⇿
0Stars
4,071Forks
14Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

3,0003,2003,4003,6003,8004,0004,2004,071112021-092024-032026-09
Major 1Minor 8Patch 5

Each point covers 5 days.

OpenSSF Scorecard 7.1 / 10
7.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-16 21:04 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 27/28 approved changesets -- score normalized to 9
10Contributorsproject has 39 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 12 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
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
PyPInarwhals>=1.15python-package/pyproject.toml
PyPInumpy>=1.21.3python-package/pyproject.toml
PyPIscipy—python-package/pyproject.toml
All dependencies 25

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

RegistryPackageVersionRelation
PyPInarwhals—direct
PyPInarwhals1.15.0direct
PyPInumpy—direct
PyPInumpy1.22.4direct
PyPIscipy—direct
PyPIscipy1.7.2direct
PyPIbuild—indirect
PyPIcffi—indirect
PyPIcffi1.15.1indirect
PyPIcloudpickle—indirect
PyPIdask—indirect
PyPIhatchling—indirect
PyPIjoblib—indirect
PyPImatplotlib—indirect
PyPIpandas—indirect
PyPIpandas1.3.4indirect
PyPIpolars—indirect
PyPIpolars1.0.0indirect
PyPIpsutil—indirect
PyPIpyarrow—indirect
PyPIpyarrow16.0.0indirect
PyPIpytest—indirect
PyPIscikit-build-core—indirect
PyPIscikit-learn—indirect
PyPIscikit-learn1.0.2indirect
Dependency advisories 0

Installing pypi:lightgbm@4.7.0 pulls in 3 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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.