Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 17:06 UTC

lyphtec / markdown-serve

Simple Markdown files server for Express or standalone

JavaScriptMIT★ 30 stars⑂ 7 forkssince Apr 2014View on GitHub ↗

lyphtec/markdown-serve holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on Vitality (57/100) and lowest on Engineering Quality (40/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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.

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

Ownership

Nguyen LyPersonal account

16 followers27 public repossince May 2011

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	markdown-serve	0.10.0	4,015	16	34 days ago	express markdown middleware markdown-serve express-middleware

Metrics by category

Vitality

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

57Moderate · 21% of overall

Development activity

45Weak

How it's scored

36/36	Push recency — last push 4 days ago
1.4/36	Commit cadence — 2/52 weeks with commits
5.4/18	Commit volume — 3 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	3
human_commit_share	0.741
days_since_last_push	4
active_weeks_last_year	2

Release discipline

76Good

How it's scored

27/27	Ships releases — 7 releases published
36/36	Release recency — latest release 32 days ago
5.4/27	Release cadence — a release every ~722.8 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	7
latest_release_tag	v0.10.0
releases_from_tags	no
days_since_latest_release	32
mean_days_between_releases	722.8

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?

44Weak · 17% of overall

Popularity & adoption

30At Risk

How it's scored

23.7/60	Stars — 30 stars
6.5/25	Forks — 7 forks
0/15	Watchers — 2 watchers

Inputs used

forks	7
stars	30
watchers	2
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	1
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

60Moderate

How it's scored

48.1/80	Monthly downloads — 4,015 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	markdown-serve
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	4,015
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?

56Moderate · 23% of overall

Maintainer resilience (bus factor)

19Critical

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	5
top_contributor_share	0.872

Issue & PR responsiveness

71Good

How it's scored

42/42	Issue resolution — 100% of issues closed
18.5/30	PR acceptance — 21/34 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 2/15 approved changesets -- score normalized to 1

Inputs used

merged_prs	21
open_issues	0
closed_issues	7
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	1
closed_unmerged_prs	13
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

52Moderate

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
8.8/25	Owner reach — 16 followers of lyphtec
22.5/25	Track record — 27 public repos, account ~15 yr old

Inputs used

followers	16
owner_type	User
is_verified	—
owner_login	lyphtec
public_repos	27
account_age_days	5,597

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 34 days ago
20/20	Version history — 16 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	markdown-serve
ecosystems	npm
any_deprecated	no
min_days_since_publish	34

Engineering Quality

Are baseline engineering and documentation practices in place?

40Weak · 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 18 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

65Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — http://lyphtec.github.io/markdown-serve/
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	http://lyphtec.github.io/markdown-serve/
docs_site	http://lyphtec.github.io/markdown-serve/
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?

50Moderate · 16% of overall

Security posture

37Weak

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 18 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 2/15 approved changesets -- score normalized to 1
0/2.5	Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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
6/7.5	Vulnerabilities — 2 existing vulnerabilities detected

Inputs used

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

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	3
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:markdown-serve@0.10.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.

54Moderate · 4% of overall

Agent context & guidance

54Moderate

How it's scored

45/45	Agent instructions — CLAUDE.md
0/15	Machine-readable docs (llms.txt)
9.3/40	Legible commit history — 7 of 40 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.175
agent_instruction_files	CLAUDE.md
agent_instruction_max_bytes	6,140

Verify loop (build / test / typecheck)

53Moderate

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
7.4/10	Demonstrated agent practice — 2 of the last 54 commits agent-authored or agent-credited
8/8	Automated maintenance — 14 of the last 54 commits are automated dependency updates
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.037
toolchain_manifests	—
dependency_bot_commit_share	0.259

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/8 source files over 60KB

Inputs used

primary_language	JavaScript
largest_source_bytes	16,461
source_files_sampled	8
oversized_source_files	0

Key facts

30GitHub stars

5contributors

3commits, last 12 months

4days since last push

7releases

1bus factor

0open 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 ★ / 7 ⇿

0Stars

7Forks

5Releases

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.

Major 0Minor 3Patch 2

Each point covers 11 days.

OpenSSF Scorecard 3.7 / 10

3.7aggregate

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-18 17:06 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 18 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 2/15 approved changesets -- score normalized to 1
0	Contributors	project has 0 contributing companies or organizations -- score normalized to 0
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
8	Vulnerabilities	2 existing vulnerabilities detected

Direct dependencies 2

Registry	Package	Version constraint	Manifest
npm	js-yaml	`^4.1.0`	package.json
npm	marked	`^15.0.2`	package.json

All dependencies 208

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

Registry	Package	Version	Relation
npm	js-yaml	`4.3.2`	direct
npm	marked	`15.0.2`	direct
npm	@babel/helper-string-parser	`7.25.9`	indirect
npm	@babel/helper-validator-identifier	`7.25.9`	indirect
npm	@babel/parser	`7.26.2`	indirect
npm	@babel/types	`7.26.0`	indirect
npm	@noble/hashes	`1.8.0`	indirect
npm	@paralleldrive/cuid2	`2.2.2`	indirect
npm	accepts	`1.3.8`	indirect
npm	acorn	`7.4.1`	indirect
npm	ansi-colors	`4.1.3`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	anymatch	`3.1.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	array-flatten	`1.1.1`	indirect
npm	asap	`2.0.6`	indirect
npm	assert-never	`1.3.0`	indirect
npm	assertion-error	`1.1.0`	indirect
npm	asynckit	`0.4.0`	indirect
npm	babel-walk	`3.0.0-canary-5`	indirect
npm	balanced-match	`1.0.0`	indirect
npm	binary-extensions	`2.3.0`	indirect
npm	body-parser	`1.20.6`	indirect
npm	brace-expansion	`1.1.18`	indirect
npm	brace-expansion	`2.1.4`	indirect
npm	braces	`3.0.3`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	bytes	`3.1.2`	indirect
npm	call-bind-apply-helpers	`1.0.2`	indirect
npm	call-bound	`1.0.4`	indirect
npm	camelcase	`6.3.0`	indirect
npm	chai	`4.5.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	character-parser	`2.2.0`	indirect
npm	check-error	`1.0.3`	indirect
npm	chokidar	`3.6.0`	indirect
npm	cliui	`7.0.4`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	combined-stream	`1.0.8`	indirect
npm	component-emitter	`1.3.1`	indirect
npm	concat-map	`0.0.1`	indirect
npm	constantinople	`4.0.1`	indirect
npm	content-disposition	`0.5.4`	indirect
npm	content-type	`1.0.5`	indirect
npm	cookie	`0.7.1`	indirect
npm	cookie-signature	`1.0.6`	indirect
npm	cookiejar	`2.1.4`	indirect
npm	debug	`2.6.9`	indirect
npm	debug	`4.3.7`	indirect
npm	debug	`4.4.3`	indirect
npm	decamelize	`4.0.0`	indirect
npm	deep-eql	`4.1.4`	indirect
npm	delayed-stream	`1.0.0`	indirect
npm	depd	`2.0.0`	indirect
npm	destroy	`1.2.0`	indirect
npm	dezalgo	`1.0.4`	indirect
npm	diff	`5.2.2`	indirect
npm	doctypes	`1.1.0`	indirect
npm	dunder-proto	`1.0.1`	indirect
npm	ee-first	`1.1.1`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	encodeurl	`1.0.2`	indirect
npm	encodeurl	`2.0.0`	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	escape-html	`1.0.3`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	etag	`1.8.1`	indirect
npm	express	`4.22.2`	indirect
npm	fast-safe-stringify	`2.1.1`	indirect
npm	fill-range	`7.1.1`	indirect
npm	finalhandler	`1.3.1`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat	`5.0.2`	indirect
npm	form-data	`4.0.6`	indirect
npm	formidable	`3.5.4`	indirect
npm	forwarded	`0.2.0`	indirect
npm	fresh	`0.5.2`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	fsevents	`2.3.3`	indirect
npm	function-bind	`1.1.2`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-func-name	`2.0.2`	indirect
npm	get-intrinsic	`1.3.0`	indirect
npm	get-proto	`1.0.1`	indirect
npm	glob	`7.1.6`	indirect
npm	glob	`8.1.0`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	gopd	`1.2.0`	indirect
npm	has-flag	`4.0.0`	indirect
npm	has-symbols	`1.1.0`	indirect
npm	has-tostringtag	`1.0.2`	indirect
npm	hasown	`2.0.4`	indirect
npm	he	`1.2.0`	indirect
npm	http-errors	`2.0.0`	indirect
npm	http-errors	`2.0.1`	indirect
npm	iconv-lite	`0.4.24`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	ipaddr.js	`1.9.1`	indirect
npm	is-binary-path	`2.1.0`	indirect
npm	is-core-module	`2.15.1`	indirect
npm	is-expression	`4.0.0`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-plain-obj	`2.1.0`	indirect
npm	is-promise	`2.2.2`	indirect
npm	is-regex	`1.2.1`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	js-stringify	`1.0.2`	indirect
npm	jstransformer	`1.0.0`	indirect
npm	locate-path	`6.0.0`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	loupe	`2.3.7`	indirect
npm	math-intrinsics	`1.1.0`	indirect
npm	media-typer	`0.3.0`	indirect
npm	merge-descriptors	`1.0.3`	indirect
npm	methods	`1.1.2`	indirect
npm	mime	`1.6.0`	indirect
npm	mime	`2.6.0`	indirect
npm	mime-db	`1.52.0`	indirect
npm	mime-types	`2.1.35`	indirect
npm	minimatch	`3.1.5`	indirect
npm	minimatch	`5.1.9`	indirect
npm	mocha	`10.8.2`	indirect
npm	ms	`2.0.0`	indirect
npm	ms	`2.1.3`	indirect
npm	negotiator	`0.6.3`	indirect
npm	normalize-path	`3.0.0`	indirect
npm	object-assign	`4.1.1`	indirect
npm	object-inspect	`1.13.4`	indirect
npm	on-finished	`2.4.1`	indirect
npm	once	`1.4.0`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	parseurl	`1.3.3`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	path-parse	`1.0.7`	indirect
npm	path-to-regexp	`0.1.13`	indirect
npm	pathval	`1.1.1`	indirect
npm	picomatch	`2.3.2`	indirect
npm	promise	`7.3.1`	indirect
npm	proxy-addr	`2.0.7`	indirect
npm	pug	`3.0.3`	indirect
npm	pug-attrs	`3.0.0`	indirect
npm	pug-code-gen	`3.0.3`	indirect
npm	pug-error	`2.1.0`	indirect
npm	pug-filters	`4.0.0`	indirect
npm	pug-lexer	`5.0.1`	indirect
npm	pug-linker	`4.0.0`	indirect
npm	pug-load	`3.0.0`	indirect
npm	pug-parser	`6.0.0`	indirect
npm	pug-runtime	`3.0.1`	indirect
npm	pug-strip-comments	`2.0.0`	indirect
npm	pug-walk	`2.0.0`	indirect
npm	qs	`6.15.3`	indirect
npm	range-parser	`1.2.1`	indirect
npm	raw-body	`2.5.3`	indirect
npm	readdirp	`3.6.0`	indirect
npm	require-directory	`2.1.1`	indirect
npm	resolve	`1.22.8`	indirect
npm	rimraf	`2.6.3`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	send	`0.19.0`	indirect
npm	serialize-javascript	`7.1.0`	indirect
npm	serve-static	`1.16.2`	indirect
npm	setprototypeof	`1.2.0`	indirect
npm	side-channel	`1.1.1`	indirect
npm	side-channel-list	`1.0.1`	indirect
npm	side-channel-map	`1.0.1`	indirect
npm	side-channel-weakmap	`1.0.2`	indirect
npm	statuses	`2.0.1`	indirect
npm	statuses	`2.0.2`	indirect
npm	string-width	`4.2.3`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	superagent	`9.0.2`	indirect
npm	supertest	`7.0.0`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	supports-preserve-symlinks-flag	`1.0.0`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	toidentifier	`1.0.1`	indirect
npm	token-stream	`1.0.0`	indirect
npm	type-detect	`4.1.0`	indirect
npm	type-is	`1.6.18`	indirect
npm	unpipe	`1.0.0`	indirect
npm	utils-merge	`1.0.1`	indirect
npm	vary	`1.1.2`	indirect
npm	void-elements	`3.1.0`	indirect
npm	with	`7.0.2`	indirect
npm	workerpool	`6.5.1`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`16.2.0`	indirect
npm	yargs-parser	`20.2.9`	indirect
npm	yargs-unparser	`2.0.0`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:markdown-serve@0.10.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.

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