Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 10:25 UTC

nodejs / llhttp

Port of http_parser to llparse

TypeScript · CMIT★ 1,948 stars⑂ 237 forkssince Feb 2018View on GitHub ↗

nodejs/llhttp holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (89/100) and lowest on Vitality (61/100). It was last updated 51 days ago. A single contributor accounts for most of its recent work.

overall / 100

Excellent

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

Ownership

Node.jsOrganization · verified domain

16,513 followers231 public repossince Nov 2014

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	llhttppoints to another repo — not scored	1.0.1	108	1	2861 days ago	http llvm ir llparse

Metrics by category

Vitality

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

61Moderate · 21% of overall

Development activity

41Weak

How it's scored

18/36	Push recency — last push 51 days ago
4.8/36	Commit cadence — 7/52 weeks with commits
16.6/18	Commit volume — 70 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	70
human_commit_share	0.36
days_since_last_push	51
active_weeks_last_year	7

Release discipline

92Excellent

How it's scored

27/27	Ships releases — 59 releases published
36/36	Release recency — latest release 51 days ago
19.8/27	Release cadence — a release every ~100.4 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	59
latest_release_tag	release/v9.4.3
releases_from_tags	no
days_since_latest_release	51
mean_days_between_releases	100.4

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?

83Excellent · 17% of overall

Popularity & adoption

82Excellent

How it's scored

53.4/60	Stars — 1,948 stars
19.8/25	Forks — 237 forks
8.9/15	Watchers — 41 watchers

Inputs used

forks	237
stars	1,948
watchers	41
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

85Excellent

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
18/18	CONTRIBUTING guide
13.5/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	yes
has_issue_template	no
has_code_of_conduct	yes
readme_badge_services	github.com
has_pull_request_template	no

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

67Good · 23% of overall

Maintainer resilience (bus factor)

41Weak

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
8.8/22.5	Commit distribution — top contributor authored 61% of commits
13.5/13.5	Contributor breadth — 61 contributors
10/10	OpenSSF Scorecard: Contributors — project has 20 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	61
top_contributor_share	0.611

Issue & PR responsiveness

65Good

How it's scored

40.5/42	Issue resolution — 96% of issues closed
14.6/30	PR acceptance — 335/687 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/16 approved changesets -- score normalized to 1

Inputs used

merged_prs	335
open_issues	6
closed_issues	165
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.965
closed_unmerged_prs	352
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

100Exceptional

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
25/25	Owner reach — 16,513 followers of nodejs
25/25	Track record — 231 public repos, account ~11 yr old

Inputs used

followers	16,513
owner_type	Organization
is_verified	yes
owner_login	nodejs
public_repos	231
account_age_days	4,316

Engineering Quality

Are baseline engineering and documentation practices in place?

89Excellent · 19% of overall

Engineering practices

82Excellent

How it's scored

24/24	CI workflows — 4 workflow(s)
24/24	Tests present
16/16	Linter config — eslint.config.mjs
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
18/20	OpenSSF Scorecard: CI-Tests — 20 out of 21 merged PRs checked by a CI test -- score normalized to 9

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

Documentation

100Exceptional

How it's scored

30/30	README
25/25	Documentation directory
15/15	Documentation / homepage site — http://llhttp.org
10/10	Repository description
10/10	Topics — 3 topics
10/10	Wiki

Inputs used

topics	llvm, llparse, http-parser
has_wiki	yes
homepage	http://llhttp.org
docs_site	http://llhttp.org
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

73Good · 16% of overall

Security posture

66Good

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
2.2/2.5	CI-Tests — 20 out of 21 merged PRs checked by a CI test -- score normalized to 9
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5	Code-Review — Found 2/16 approved changesets -- score normalized to 1
2.5/2.5	Contributors — project has 20 contributing companies or organizations
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5	Dependency-Update-Tool — update tool detected
5/5	Fuzzing — project is 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
5/5	Pinned-Dependencies — all dependencies are pinned
4.5/5	SAST — SAST tool detected but not run on all commits
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
7.5/7.5	Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5	Vulnerabilities — 11 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	6.6

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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	12
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:llhttp@1.0.1 runtime dependency closure — what installing the published package pulls in — 12 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.

78Good · 4% of overall

Agent context & guidance

40Weak

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.778
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

90Excellent

How it's scored

18/18	One-command bootstrap — Makefile
22/22	Automated tests
11/11	Lint / format config — eslint.config.mjs
11/11	Static type checking — tsconfig.json
10/10	Reproducible environment — Dockerfile, lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
8/8	Automated maintenance — 64 of the last 100 commits are automated dependency updates
10/10	OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned

Inputs used

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

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — TypeScript (statically typed)
55/55	Manageable file sizes — 0/19 source files over 60KB

Inputs used

primary_language	TypeScript
largest_source_bytes	46,738
source_files_sampled	19
oversized_source_files	0

Machine-readable interfaces

100Exceptional

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
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

1,948GitHub stars

61contributors

70commits, last 12 months

51days since last push

59releases

1bus factor

6open issues

npmpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
npm package 'llhttp' points at a different repository (https://github.com/indutny/llhttp); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 237 ⇿

0Stars

237Forks

59Releases

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 1Minor 2Patch 12

Each point covers 8 days.

OpenSSF Scorecard 6.6 / 10

6.6aggregate

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-20 10:25 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
9	CI-Tests	20 out of 21 merged PRs checked by a CI test -- score normalized to 9
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
1	Code-Review	Found 2/16 approved changesets -- score normalized to 1
10	Contributors	project has 20 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
10	Fuzzing	project is 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
10	Pinned-Dependencies	all dependencies are pinned
9	SAST	SAST tool detected but not run on all commits
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
10	Token-Permissions	GitHub workflow tokens follow principle of least privilege
0	Vulnerabilities	11 existing vulnerabilities detected

Direct dependencies 1

Registry	Package	Version constraint	Manifest
npm	llparse	`^7.3.1`	package.json

All dependencies 166

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

Registry	Package	Version	Relation
npm	llparse	`7.3.1`	direct
npm	@esbuild/aix-ppc64	`0.27.3`	indirect
npm	@esbuild/android-arm	`0.27.3`	indirect
npm	@esbuild/android-arm64	`0.27.3`	indirect
npm	@esbuild/android-x64	`0.27.3`	indirect
npm	@esbuild/darwin-arm64	`0.27.3`	indirect
npm	@esbuild/darwin-x64	`0.27.3`	indirect
npm	@esbuild/freebsd-arm64	`0.27.3`	indirect
npm	@esbuild/freebsd-x64	`0.27.3`	indirect
npm	@esbuild/linux-arm	`0.27.3`	indirect
npm	@esbuild/linux-arm64	`0.27.3`	indirect
npm	@esbuild/linux-ia32	`0.27.3`	indirect
npm	@esbuild/linux-loong64	`0.27.3`	indirect
npm	@esbuild/linux-mips64el	`0.27.3`	indirect
npm	@esbuild/linux-ppc64	`0.27.3`	indirect
npm	@esbuild/linux-riscv64	`0.27.3`	indirect
npm	@esbuild/linux-s390x	`0.27.3`	indirect
npm	@esbuild/linux-x64	`0.27.3`	indirect
npm	@esbuild/netbsd-arm64	`0.27.3`	indirect
npm	@esbuild/netbsd-x64	`0.27.3`	indirect
npm	@esbuild/openbsd-arm64	`0.27.3`	indirect
npm	@esbuild/openbsd-x64	`0.27.3`	indirect
npm	@esbuild/openharmony-arm64	`0.27.3`	indirect
npm	@esbuild/sunos-x64	`0.27.3`	indirect
npm	@esbuild/win32-arm64	`0.27.3`	indirect
npm	@esbuild/win32-ia32	`0.27.3`	indirect
npm	@esbuild/win32-x64	`0.27.3`	indirect
npm	@eslint-community/eslint-utils	`4.9.1`	indirect
npm	@eslint-community/regexpp	`4.12.2`	indirect
npm	@eslint/config-array	`0.23.5`	indirect
npm	@eslint/config-helpers	`0.5.5`	indirect
npm	@eslint/core	`1.2.1`	indirect
npm	@eslint/js	`10.0.1`	indirect
npm	@eslint/object-schema	`3.0.5`	indirect
npm	@eslint/plugin-kit	`0.7.1`	indirect
npm	@humanfs/core	`0.19.1`	indirect
npm	@humanfs/node	`0.16.6`	indirect
npm	@humanwhocodes/module-importer	`1.0.1`	indirect
npm	@humanwhocodes/retry	`0.3.1`	indirect
npm	@humanwhocodes/retry	`0.4.2`	indirect
npm	@stylistic/eslint-plugin	`5.10.0`	indirect
npm	@types/debug	`4.1.5`	indirect
npm	@types/esrecurse	`4.3.1`	indirect
npm	@types/estree	`1.0.8`	indirect
npm	@types/json-schema	`7.0.15`	indirect
npm	@types/markdown-it	`0.0.4`	indirect
npm	@types/node	`25.6.0`	indirect
npm	@typescript-eslint/eslint-plugin	`8.59.1`	indirect
npm	@typescript-eslint/parser	`8.59.1`	indirect
npm	@typescript-eslint/project-service	`8.59.1`	indirect
npm	@typescript-eslint/scope-manager	`8.59.1`	indirect
npm	@typescript-eslint/tsconfig-utils	`8.59.1`	indirect
npm	@typescript-eslint/type-utils	`8.59.1`	indirect
npm	@typescript-eslint/types	`8.59.1`	indirect
npm	@typescript-eslint/typescript-estree	`8.59.1`	indirect
npm	@typescript-eslint/utils	`8.59.1`	indirect
npm	@typescript-eslint/visitor-keys	`8.59.1`	indirect
npm	acorn	`8.16.0`	indirect
npm	acorn-jsx	`5.3.2`	indirect
npm	ajv	`6.14.0`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	argparse	`1.0.10`	indirect
npm	balanced-match	`4.0.4`	indirect
npm	binary-search	`1.3.6`	indirect
npm	brace-expansion	`5.0.4`	indirect
npm	camelcase	`5.3.1`	indirect
npm	cliui	`6.0.0`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`3.2.7`	indirect
npm	debug	`4.4.3`	indirect
npm	decamelize	`1.2.0`	indirect
npm	deep-is	`0.1.4`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	entities	`1.1.2`	indirect
npm	esbuild	`0.27.3`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	eslint	`10.2.1`	indirect
npm	eslint-scope	`9.1.2`	indirect
npm	eslint-visitor-keys	`3.4.3`	indirect
npm	eslint-visitor-keys	`4.2.1`	indirect
npm	eslint-visitor-keys	`5.0.1`	indirect
npm	espree	`10.4.0`	indirect
npm	espree	`11.2.0`	indirect
npm	esquery	`1.7.0`	indirect
npm	esrecurse	`4.3.0`	indirect
npm	estraverse	`5.3.0`	indirect
npm	esutils	`2.0.3`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-json-stable-stringify	`2.1.0`	indirect
npm	fast-levenshtein	`2.0.6`	indirect
npm	fdir	`6.5.0`	indirect
npm	file-entry-cache	`8.0.0`	indirect
npm	find-up	`4.1.0`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat-cache	`4.0.1`	indirect
npm	flatted	`3.4.2`	indirect
npm	fsevents	`2.3.3`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-tsconfig	`4.8.1`	indirect
npm	glob-parent	`6.0.2`	indirect
npm	ignore	`5.3.2`	indirect
npm	ignore	`7.0.5`	indirect
npm	imurmurhash	`0.1.4`	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	isexe	`2.0.0`	indirect
npm	json-buffer	`3.0.1`	indirect
npm	json-schema-traverse	`0.4.1`	indirect
npm	json-stable-stringify-without-jsonify	`1.0.1`	indirect
npm	keyv	`4.5.4`	indirect
npm	levn	`0.4.1`	indirect
npm	linkify-it	`2.2.0`	indirect
npm	llparse-builder	`1.5.2`	indirect
npm	llparse-dot	`1.0.1`	indirect
npm	llparse-frontend	`3.0.0`	indirect
npm	llparse-test-fixture	`5.1.0`	indirect
npm	locate-path	`5.0.0`	indirect
npm	locate-path	`6.0.0`	indirect
npm	markdown-it	`8.4.2`	indirect
npm	mdgator	`1.1.2`	indirect
npm	mdurl	`1.0.1`	indirect
npm	minimatch	`10.2.4`	indirect
npm	ms	`2.1.3`	indirect
npm	natural-compare	`1.4.0`	indirect
npm	optionator	`0.9.4`	indirect
npm	p-limit	`2.3.0`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`4.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	p-try	`2.2.0`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	picomatch	`4.0.4`	indirect
npm	prelude-ls	`1.2.1`	indirect
npm	punycode	`2.3.1`	indirect
npm	require-directory	`2.1.1`	indirect
npm	require-main-filename	`2.0.0`	indirect
npm	resolve-pkg-maps	`1.0.0`	indirect
npm	semver	`7.7.4`	indirect
npm	set-blocking	`2.0.0`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	sprintf-js	`1.0.3`	indirect
npm	string-width	`4.2.3`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	tinyglobby	`0.2.16`	indirect
npm	ts-api-utils	`2.5.0`	indirect
npm	tsx	`4.21.0`	indirect
npm	type-check	`0.4.0`	indirect
npm	typescript	`5.9.3`	indirect
npm	typescript-eslint	`8.59.1`	indirect
npm	uc.micro	`1.0.6`	indirect
npm	undici-types	`7.19.2`	indirect
npm	uri-js	`4.4.1`	indirect
npm	which	`2.0.2`	indirect
npm	which-module	`2.0.1`	indirect
npm	word-wrap	`1.2.5`	indirect
npm	wrap-ansi	`6.2.0`	indirect
npm	y18n	`4.0.3`	indirect
npm	yargs	`15.4.1`	indirect
npm	yargs-parser	`18.1.3`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:llhttp@1.0.1 pulls in 12 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