Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-06 02:14 UTC

lightningdevkit / rust-lightning

Active development happens on git.rust-bitcoin.org, this repo is a mirror of https://git.rust-bitcoin.org/lightningdevkit/rust-lightning

RustCustom license★ 1,368 stars⑂ 477 forkssince Feb 2018View on GitHub ↗

lightningdevkit/rust-lightning holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Vitality (95/100) and lowest on Security (70/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

Lightning Dev KitOrganization
518 followers19 public repossince Jan 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iolightning0.2.595,475740 days ago
crates.iopossiblyrandom0.2.153,899448 days ago
crates.iolightning-types0.3.5120,189160 days ago
crates.iolightning-macros0.2.144,4616188 days ago
crates.iolightning-invoice0.34.1140,9515313 days agobitcoinbolt11invoicelightning

Metrics by category

Vitality

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

95Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recencylast push 0 days ago
36/36Commit cadence52/52 weeks with commits
18/18Commit volume1,902 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,902
human_commit_share1
days_since_last_push0
active_weeks_last_year52
How it's scored
16.2/27Ships releases65 version tags (no GitHub releases)
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~32.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count65
latest_release_tagv0.2.5
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases32.9
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?

79Good · 17% of overall
How it's scored
50.9/60Stars1,368 stars
22.3/25Forks477 forks
9.4/15Watchers50 watchers
Inputs used
forks477
stars1,368
watchers50
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
0/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_templateno
How it's scored
75.4/80Monthly downloads454,975 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageslightning, possiblyrandom, lightning-types, lightning-macros, lightning-invoice
dependents
ecosystemscrates
total_downloads6,104,512
monthly_downloads454,975
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?

78Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.5/22.5Commit distributiontop contributor authored 49% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 34 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.491
How it's scored
32.2/42Issue resolution77% of issues closed
24.8/30PR acceptance2,917/3,530 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 14/30 approved changesets -- score normalized to 4
Inputs used
merged_prs2,917
open_issues273
closed_issues898
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.767
closed_unmerged_prs613
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
0/20Verified domainverified-domain status not read for this organization
19.5/25Owner reach518 followers of lightningdevkit
21.5/25Track record19 public repos, account ~6 yr old
Inputs used
followers518
owner_typeOrganization
is_verified
owner_loginlightningdevkit
public_repos19
account_age_days2,379
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable5 package(s) on crates
35/35Publish recencylatest publish 0 days ago
20/20Version history74 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageslightning, possiblyrandom, lightning-types, lightning-macros, lightning-invoice
ecosystemscrates
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://git.rust-bitcoin.org/lightningdevkit/rust-lightning
10/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicsbitcoin, lightning-network
has_wikiyes
homepagehttps://git.rust-bitcoin.org/lightningdevkit/rust-lightning
docs_sitehttps://git.rust-bitcoin.org/lightningdevkit/rust-lightning
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 14/30 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 34 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
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_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate7
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, 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.

73Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history88 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.88
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes1,490
How it's scored
12.6/18One-command bootstrapCargo.toml, bench/Cargo.toml, ext-functional-test-demo/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice9 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.09
toolchain_manifestsCargo.toml, bench/Cargo.toml, ext-functional-test-demo/Cargo.toml, fuzz/Cargo.toml, fuzz/fuzz-fake-hashes/Cargo.toml, fuzz/fuzz-real-hashes/Cargo.toml, fuzz/write-seeds/Cargo.toml, lightning-background-processor/Cargo.toml, lightning-block-sync/Cargo.toml, lightning-custom-message/Cargo.toml, lightning-dns-resolver/Cargo.toml, lightning-invoice/Cargo.toml, lightning-liquidity/Cargo.toml, lightning-macros/Cargo.toml, lightning-net-tokio/Cargo.toml, lightning-persister/Cargo.toml, lightning-rapid-gossip-sync/Cargo.toml, lightning-tests/Cargo.toml, lightning-transaction-sync/Cargo.toml, lightning-types/Cargo.toml, lightning/Cargo.toml, msrv-no-dev-deps-check/Cargo.toml, no-std-check/Cargo.toml, possiblyrandom/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
47.4/55Manageable file sizes54/389 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes910,809
source_files_sampled389
oversized_source_files54

Key facts

1,368GitHub stars
99contributors
1,902commits, last 12 months
0days since last push
65releases
2bus factor
273open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'lightning-bench' from its registry
  • Could not fetch crates package 'no-std-check' from its registry
  • Could not fetch crates package 'lightning-tests' from its registry
  • deps.dev does not index crates:lightning@0.2.5; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 477 ⇿
0Stars
477Forks
62Releases

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.

010020030040050045992018-022022-052026-07
Major 0Minor 0Patch 48

Each point covers 8 days.

OpenSSF Scorecard 7.0 / 10
7.0aggregate

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-06 02:14 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
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 14/30 approved changesets -- score normalized to 4
10Contributorsproject has 34 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 91
RegistryPackageVersion constraintManifest
crates.iolightningbench/Cargo.toml
crates.iolightning-persisterbench/Cargo.toml
crates.iolightning-rapid-gossip-syncbench/Cargo.toml
crates.iocriterion0.4bench/Cargo.toml
crates.iolightningext-functional-test-demo/Cargo.toml
crates.iobitcoin0.32.2lightning-background-processor/Cargo.toml
crates.iobitcoin_hashes0.14.0lightning-background-processor/Cargo.toml
crates.iobitcoin-io0.1.2lightning-background-processor/Cargo.toml
crates.iolightning0.3.0lightning-background-processor/Cargo.toml
crates.iolightning-rapid-gossip-sync0.3.0lightning-background-processor/Cargo.toml
crates.iolightning-liquidity0.3.0lightning-background-processor/Cargo.toml
crates.iopossiblyrandom0.2lightning-background-processor/Cargo.toml
crates.iobitcoin0.32.2lightning-block-sync/Cargo.toml
crates.iolightning0.3.0lightning-block-sync/Cargo.toml
crates.iotokio1.35lightning-block-sync/Cargo.toml
crates.ioserde_json1.0lightning-block-sync/Cargo.toml
crates.iobitreq0.3lightning-block-sync/Cargo.toml
crates.iobitcoin0.32.2lightning-custom-message/Cargo.toml
crates.iolightning0.3.0lightning-custom-message/Cargo.toml
crates.iolightning0.3.0lightning-dns-resolver/Cargo.toml
crates.iolightning-types0.4.0lightning-dns-resolver/Cargo.toml
crates.iodnssec-prover0.6lightning-dns-resolver/Cargo.toml
crates.iotokio1.0lightning-dns-resolver/Cargo.toml
crates.iobech320.11.0lightning-invoice/Cargo.toml
crates.iolightning-types0.4.0lightning-invoice/Cargo.toml
crates.ioserde1.0lightning-invoice/Cargo.toml
crates.iobitcoin0.32.7lightning-invoice/Cargo.toml
crates.iolightning0.3.0lightning-liquidity/Cargo.toml
crates.iolightning-types0.4.0lightning-liquidity/Cargo.toml
crates.iolightning-invoice0.35.0lightning-liquidity/Cargo.toml
crates.iolightning-macros0.2lightning-liquidity/Cargo.toml
crates.iobitcoin0.32.2lightning-liquidity/Cargo.toml
crates.iochrono0.4lightning-liquidity/Cargo.toml
crates.ioserde1.0lightning-liquidity/Cargo.toml
crates.ioserde_json1.0lightning-liquidity/Cargo.toml
crates.iobacktrace0.3lightning-liquidity/Cargo.toml
crates.iobitreq0.3.2lightning-liquidity/Cargo.toml
crates.iosyn2.0lightning-macros/Cargo.toml
crates.ioproc-macro21.0lightning-macros/Cargo.toml
crates.ioquote1.0lightning-macros/Cargo.toml
crates.iobitcoin0.32.2lightning-net-tokio/Cargo.toml
crates.iolightning0.3.0lightning-net-tokio/Cargo.toml
crates.iotokio1.35lightning-net-tokio/Cargo.toml
crates.iobitcoin0.32.2lightning-persister/Cargo.toml
crates.iolightning0.3.0lightning-persister/Cargo.toml
crates.iotokio1.35lightning-persister/Cargo.toml
crates.iolightning0.3.0lightning-rapid-gossip-sync/Cargo.toml
crates.iobitcoin0.32.2lightning-rapid-gossip-sync/Cargo.toml
crates.iobitcoin_hashes0.14.0lightning-rapid-gossip-sync/Cargo.toml
crates.iobitcoin-io0.1.2lightning-rapid-gossip-sync/Cargo.toml
crates.iolightning-typeslightning-tests/Cargo.toml
crates.iolightning-invoicelightning-tests/Cargo.toml
crates.iolightning-macroslightning-tests/Cargo.toml
crates.iolightninglightning-tests/Cargo.toml
crates.iolightning_0_20.2.0lightning-tests/Cargo.toml
crates.iolightning_0_10.1.7lightning-tests/Cargo.toml
crates.iolightning_0_0_1250.0.125lightning-tests/Cargo.toml
crates.iobitcoin0.32.2lightning-tests/Cargo.toml
crates.iolightning0.3.0lightning-transaction-sync/Cargo.toml
crates.iolightning-macros0.2lightning-transaction-sync/Cargo.toml
crates.iobitcoin0.32.2lightning-transaction-sync/Cargo.toml
crates.iofutures0.3lightning-transaction-sync/Cargo.toml
crates.ioesplora-client0.13lightning-transaction-sync/Cargo.toml
crates.ioelectrum-client0.25lightning-transaction-sync/Cargo.toml
crates.iobitcoin0.32.2lightning-types/Cargo.toml
crates.iolightning-types0.4.0lightning/Cargo.toml
crates.iolightning-invoice0.35.0lightning/Cargo.toml
crates.iolightning-macros0.2lightning/Cargo.toml
crates.iobech320.11.0lightning/Cargo.toml
crates.iobitcoin0.32.4lightning/Cargo.toml
crates.iochacha20-poly13050.2.0lightning/Cargo.toml
crates.iodnssec-prover0.6lightning/Cargo.toml
crates.iohashbrown0.13lightning/Cargo.toml
crates.iopossiblyrandom0.2lightning/Cargo.toml
crates.ioregex1.5.6lightning/Cargo.toml
crates.iobacktrace0.3lightning/Cargo.toml
crates.iolibm0.2lightning/Cargo.toml
crates.ioinventory0.3lightning/Cargo.toml
crates.iolightningmsrv-no-dev-deps-check/Cargo.toml
crates.iolightning-block-syncmsrv-no-dev-deps-check/Cargo.toml
crates.iolightning-invoicemsrv-no-dev-deps-check/Cargo.toml
crates.iolightning-net-tokiomsrv-no-dev-deps-check/Cargo.toml
crates.iolightning-persistermsrv-no-dev-deps-check/Cargo.toml
crates.iolightning-background-processormsrv-no-dev-deps-check/Cargo.toml
crates.iolightning-rapid-gossip-syncmsrv-no-dev-deps-check/Cargo.toml
crates.iolightning-custom-messagemsrv-no-dev-deps-check/Cargo.toml
crates.iolightningno-std-check/Cargo.toml
crates.iolightning-invoiceno-std-check/Cargo.toml
crates.iolightning-rapid-gossip-syncno-std-check/Cargo.toml
crates.iolightning-background-processorno-std-check/Cargo.toml
crates.iogetrandom0.2possiblyrandom/Cargo.toml
All dependencies 39

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

RegistryPackageVersionRelation
crates.iobacktracedirect
crates.iobech32direct
crates.iobitcoindirect
crates.iobitcoin-iodirect
crates.iobitcoin_hashesdirect
crates.iobitreqdirect
crates.iochacha20-poly1305direct
crates.iochronodirect
crates.iocriteriondirect
crates.iodnssec-proverdirect
crates.ioelectrum-clientdirect
crates.ioesplora-clientdirect
crates.iofuturesdirect
crates.iogetrandomdirect
crates.iohashbrowndirect
crates.ioinventorydirect
crates.iolibmdirect
crates.iolightningdirect
crates.iolightning-invoicedirect
crates.iolightning-liquiditydirect
crates.iolightning-macrosdirect
crates.iolightning-persisterdirect
crates.iolightning-rapid-gossip-syncdirect
crates.iolightning-typesdirect
crates.iopossiblyrandomdirect
crates.ioproc-macro2direct
crates.ioquotedirect
crates.ioregexdirect
crates.ioserdedirect
crates.ioserde_jsondirect
crates.iosyndirect
crates.iotokiodirect
crates.ioaflindirect
crates.iobitcoindindirect
crates.ioelectrsdindirect
crates.iohonggfuzzindirect
crates.iolibfuzzer-sysindirect
crates.ioparking_lotindirect
crates.iowindows-sysindirect
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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.