Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-27 15:05 UTC

alexbosworth / ln-sync

Methods for syncing Lightning Network records

JavaScriptMIT★ 2 stars⑂ 3 forkssince Jun 2020View on GitHub ↗

alexbosworth/ln-sync holds a health index of 33 out of 100, placing it in the At Risk band. It scores highest on Security (54/100) and lowest on Vitality (23/100). It was last updated 32 days ago. A single contributor accounts for most of its recent work.

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.

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)

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

Ownership

Alex BosworthPersonal account

658 followers126 public repossince Sep 2010

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	ln-sync	8.0.6	3,514	97	32 days ago	lnd lightning lightning-network

Metrics by category

Vitality

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

23At Risk · 21% of overall

Development activity

37Weak

How it's scored

18/36	Push recency — last push 32 days ago
6.9/36	Commit cadence — 10/52 weeks with commits
10.3/18	Commit volume — 13 commits in the last year
2/10	OpenSSF Scorecard: Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2

Inputs used

commits_last_year	13
human_commit_share	1
days_since_last_push	32
active_weeks_last_year	10

Release discipline

1Critical

How it's scored

0/27	Ships releases — no releases published
0/36	Release recency — no releases
0/27	Release cadence — no releases
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count

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?

33At Risk · 17% of overall

Popularity & adoption

2Critical

How it's scored

0/60	Stars — 2 stars
2.5/25	Forks — 3 forks
0/15	Watchers — 1 watchers

Inputs used

forks	3
stars	2
watchers	1
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

59Moderate

How it's scored

47.3/80	Monthly downloads — 3,514 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	ln-sync
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	3,514
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?

49Weak · 23% of overall

Maintainer resilience (bus factor)

25At Risk

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
2.2/22.5	Commit distribution — top contributor authored 90% of commits
4.1/13.5	Contributor breadth — 3 contributors
10/10	OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10

Inputs used

bus_factor	1
contributors_sampled	3
top_contributor_share	0.902

Issue & PR responsiveness

17Critical

How it's scored

0/42	Issue resolution — 0% of issues closed
13.1/30	PR acceptance — 7/16 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15	OpenSSF Scorecard: Code-Review — Found 3/23 approved changesets -- score normalized to 1

Inputs used

merged_prs	7
open_issues	1
closed_issues	0
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0
closed_unmerged_prs	9
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

69Good

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
20.3/25	Owner reach — 658 followers of alexbosworth
25/25	Track record — 126 public repos, account ~16 yr old

Inputs used

followers	658
owner_type	User
is_verified	—
owner_login	alexbosworth
public_repos	126
account_age_days	5,855

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on npm
35/35	Publish recency — latest publish 32 days ago
20/20	Version history — 97 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	ln-sync
ecosystems	npm
any_deprecated	no
min_days_since_publish	32

Engineering Quality

Are baseline engineering and documentation practices in place?

34At Risk · 19% of overall

Engineering practices

24At Risk

How it's scored

0/24	CI workflows
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0

Inputs used

has_ci	no
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

50Moderate

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

54Moderate · 16% of overall

Security posture

43Weak

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5	Code-Review — Found 3/23 approved changesets -- score normalized to 1
2.5/2.5	Contributors — project has 3 contributing companies or organizations -- score normalized to 10
0/10	Dangerous-Workflow — no data
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
1.5/7.5	Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
7.5/7.5	Vulnerabilities — 0 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	13
scorecard_version	v5.5.0
checks_inconclusive	5
scorecard_aggregate	4.2

Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	127
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:ln-sync@8.0.6 runtime dependency closure — what installing the published package pulls in — 127 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.

27At Risk · 4% of overall

Agent context & guidance

1Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
1.1/40	Legible commit history — 2 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.02
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

36Weak

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
0/11	Static type checking
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	no
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

55Moderate

How it's scored

0/45	Type-checkable code — JavaScript without a type-check config
55/55	Manageable file sizes — 0/184 source files over 60KB

Inputs used

primary_language	JavaScript
largest_source_bytes	16,725
source_files_sampled	184
oversized_source_files	0

Key facts

2GitHub stars

3contributors

13commits, last 12 months

32days since last push

0releases

1bus factor

1open issues

npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 3 ⇿

0Stars

3Forks

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.

Each point covers 4 days.

OpenSSF Scorecard 4.2 / 10

4.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-09-27 15:05 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
0	CI-Tests	0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
1	Code-Review	Found 3/23 approved changesets -- score normalized to 1
10	Contributors	project has 3 contributing companies or organizations -- score normalized to 10
n/a	Dangerous-Workflow	no workflows found
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
2	Maintained	3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
10	Vulnerabilities	0 existing vulnerabilities detected

Direct dependencies 10

Registry	Package	Version constraint	Manifest
npm	@alexbosworth/blockchain	`4.5.1`	package.json
npm	async	`3.2.6`	package.json
npm	asyncjs-util	`1.2.12`	package.json
npm	bech32	`2.0.0`	package.json
npm	bolt07	`2.0.0`	package.json
npm	colorette	`2.0.20`	package.json
npm	ecpair	`2.1.0`	package.json
npm	ln-service	`59.3.4`	package.json
npm	psbt	`6.0.0`	package.json
npm	tiny-secp256k1	`2.2.4`	package.json

All dependencies 174

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

Registry	Package	Version	Relation
npm	@alexbosworth/blockchain	`4.5.1`	direct
npm	async	`3.2.4`	direct
npm	async	`3.2.6`	direct
npm	asyncjs-util	`1.2.12`	direct
npm	bech32	`2.0.0`	direct
npm	bolt07	`1.9.5`	direct
npm	bolt07	`2.0.0`	direct
npm	colorette	`2.0.20`	direct
npm	ecpair	`2.1.0`	direct
npm	ln-service	`59.3.4`	direct
npm	psbt	`6.0.0`	direct
npm	tiny-secp256k1	`2.2.4`	direct
npm	@alexbosworth/node-fetch	`2.6.2`	indirect
npm	@balena/dockerignore	`1.0.2`	indirect
npm	@grpc/grpc-js	`1.14.4`	indirect
npm	@grpc/proto-loader	`0.7.15`	indirect
npm	@grpc/proto-loader	`0.8.1`	indirect
npm	@js-sdsl/ordered-map	`4.4.2`	indirect
npm	@noble/hashes	`1.8.0`	indirect
npm	@protobufjs/aspromise	`1.1.2`	indirect
npm	@protobufjs/base64	`1.1.2`	indirect
npm	@protobufjs/codegen	`2.0.5`	indirect
npm	@protobufjs/eventemitter	`1.1.1`	indirect
npm	@protobufjs/fetch	`1.1.1`	indirect
npm	@protobufjs/float	`1.0.2`	indirect
npm	@protobufjs/path	`1.1.2`	indirect
npm	@protobufjs/pool	`1.1.0`	indirect
npm	@protobufjs/utf8	`1.1.2`	indirect
npm	@types/caseless	`0.12.5`	indirect
npm	@types/node	`26.2.0`	indirect
npm	@types/request	`2.48.13`	indirect
npm	@types/tough-cookie	`4.0.5`	indirect
npm	@types/ws	`8.18.1`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	asn1	`0.2.6`	indirect
npm	asynckit	`0.4.0`	indirect
npm	available-typed-arrays	`1.0.7`	indirect
npm	b4a	`1.8.1`	indirect
npm	bare-events	`2.9.1`	indirect
npm	bare-fs	`4.8.1`	indirect
npm	bare-path	`3.1.1`	indirect
npm	bare-stream	`2.13.3`	indirect
npm	bare-url	`2.5.2`	indirect
npm	base-x	`3.0.11`	indirect
npm	base-x	`4.0.1`	indirect
npm	base64-js	`1.5.1`	indirect
npm	bcrypt-pbkdf	`1.0.2`	indirect
npm	bip174	`2.1.1`	indirect
npm	bip66	`2.0.0`	indirect
npm	bitcoin-ops	`1.4.1`	indirect
npm	bitcoinjs-lib	`6.1.7`	indirect
npm	bl	`4.1.0`	indirect
npm	bn.js	`5.2.3`	indirect
npm	bn.js	`5.2.5`	indirect
npm	bolt09	`2.2.0`	indirect
npm	bolt09	`3.0.0`	indirect
npm	bs58	`4.0.1`	indirect
npm	bs58	`5.0.0`	indirect
npm	bs58check	`2.1.2`	indirect
npm	bs58check	`3.0.1`	indirect
npm	buffer	`5.7.1`	indirect
npm	buildcheck	`0.0.7`	indirect
npm	call-bind	`1.0.9`	indirect
npm	call-bind-apply-helpers	`1.0.2`	indirect
npm	call-bound	`1.0.4`	indirect
npm	chownr	`1.1.4`	indirect
npm	cipher-base	`1.0.7`	indirect
npm	cliui	`8.0.1`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	combined-stream	`1.0.8`	indirect
npm	core-util-is	`1.0.3`	indirect
npm	cpu-features	`0.0.10`	indirect
npm	create-hash	`1.2.0`	indirect
npm	debug	`4.4.3`	indirect
npm	define-data-property	`1.1.4`	indirect
npm	delayed-stream	`1.0.0`	indirect
npm	docker-modem	`5.0.7`	indirect
npm	dockerode	`5.0.1`	indirect
npm	dunder-proto	`1.0.1`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	end-of-stream	`1.4.5`	indirect
npm	es-define-property	`1.0.1`	indirect
npm	es-errors	`1.3.0`	indirect
npm	es-object-atoms	`1.1.2`	indirect
npm	es-set-tostringtag	`2.1.0`	indirect
npm	escalade	`3.2.0`	indirect
npm	events-universal	`1.0.1`	indirect
npm	fast-fifo	`1.3.2`	indirect
npm	find-free-ports	`3.1.1`	indirect
npm	for-each	`0.3.5`	indirect
npm	form-data	`2.5.6`	indirect
npm	fs-constants	`1.0.0`	indirect
npm	function-bind	`1.1.2`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-intrinsic	`1.3.0`	indirect
npm	get-proto	`1.0.1`	indirect
npm	gopd	`1.2.0`	indirect
npm	has-property-descriptors	`1.0.2`	indirect
npm	has-symbols	`1.1.0`	indirect
npm	has-tostringtag	`1.0.2`	indirect
npm	hash-base	`3.1.2`	indirect
npm	hasown	`2.0.4`	indirect
npm	ieee754	`1.2.1`	indirect
npm	inherits	`2.0.4`	indirect
npm	invoices	`5.0.2`	indirect
npm	invoices	`6.1.3`	indirect
npm	is-callable	`1.2.7`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-typed-array	`1.1.15`	indirect
npm	isarray	`1.0.0`	indirect
npm	isarray	`2.0.5`	indirect
npm	lightning	`12.2.8`	indirect
npm	ln-docker-daemons	`8.0.4`	indirect
npm	lodash.camelcase	`4.3.0`	indirect
npm	long	`5.3.2`	indirect
npm	macaroon	`3.0.4`	indirect
npm	math-intrinsics	`1.1.0`	indirect
npm	md5.js	`1.3.5`	indirect
npm	mime-db	`1.52.0`	indirect
npm	mime-types	`2.1.35`	indirect
npm	mkdirp-classic	`0.5.3`	indirect
npm	mock-lnd	`4.0.0`	indirect
npm	ms	`2.1.3`	indirect
npm	nan	`2.28.0`	indirect
npm	once	`1.4.0`	indirect
npm	possible-typed-array-names	`1.1.0`	indirect
npm	process-nextick-args	`2.0.1`	indirect
npm	protobufjs	`7.6.5`	indirect
npm	pump	`3.0.4`	indirect
npm	pushdata-bitcoin	`1.0.1`	indirect
npm	randombytes	`2.1.0`	indirect
npm	readable-stream	`2.3.8`	indirect
npm	readable-stream	`3.6.2`	indirect
npm	require-directory	`2.1.1`	indirect
npm	ripemd160	`2.0.3`	indirect
npm	safe-buffer	`5.1.2`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	set-function-length	`1.2.2`	indirect
npm	sha.js	`2.4.12`	indirect
npm	sjcl	`1.0.9`	indirect
npm	split-ca	`1.0.1`	indirect
npm	ssh2	`1.17.0`	indirect
npm	streamx	`2.28.0`	indirect
npm	string-width	`4.2.3`	indirect
npm	string_decoder	`1.1.1`	indirect
npm	string_decoder	`1.3.0`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	tagged-tag	`1.0.0`	indirect
npm	tar-fs	`2.1.5`	indirect
npm	tar-stream	`2.2.0`	indirect
npm	tar-stream	`3.2.0`	indirect
npm	teex	`1.0.1`	indirect
npm	text-decoder	`1.2.7`	indirect
npm	to-buffer	`1.2.2`	indirect
npm	tweetnacl	`0.14.5`	indirect
npm	tweetnacl	`1.0.3`	indirect
npm	tweetnacl-util	`0.15.1`	indirect
npm	type-fest	`5.8.0`	indirect
npm	typed-array-buffer	`1.0.3`	indirect
npm	typeforce	`1.18.0`	indirect
npm	uint8array-tools	`0.0.7`	indirect
npm	undici-types	`8.3.0`	indirect
npm	util-deprecate	`1.0.2`	indirect
npm	varuint-bitcoin	`1.1.2`	indirect
npm	which-typed-array	`1.1.22`	indirect
npm	wif	`2.0.6`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`17.7.3`	indirect
npm	yargs-parser	`21.1.1`	indirect

Dependency advisories 0

Installing npm:ln-sync@8.0.6 pulls in 127 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.

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 — npm.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records