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

fastify / fastify

Fast and low overhead web framework, for Node.js

JavaScriptMIT★ 37,145 stars⑂ 3,018 forkssince Sep 2016View on GitHub ↗

fastify/fastify holds a health index of 99 out of 100, placing it in the Exceptional band. It scores highest on Vitality (99/100) and lowest on AI Readiness (67/100). It was last updated today. 4 contributors account for most of its recent work.

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

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

Ownership

FastifyOrganization · verified domain
1,279 followers140 public repossince Jan 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmfastify5.12.544,413,2583310 days agowebframeworkjsonschemaopenapi

Metrics by category

Vitality

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

99Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 352 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year352
human_commit_share0.95
days_since_last_push0
active_weeks_last_year51

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~4.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv5.12.5
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases4.3

Community & Adoption

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

97Exceptional · 17% of overall
How it's scored
60/60Stars — 37,145 stars
25/25Forks — 3,018 forks
14.3/15Watchers — 368 watchers
Inputs used
forks3,018
stars37,145
watchers368
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges11
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io, www.bestpractices.dev
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 44,413,258 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesfastify
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads44,413,258
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?

89Excellent · 23% of overall
How it's scored
43.2/54Bus factor — 4 contributor(s) cover half of all commits
17.6/22.5Commit distribution — top contributor authored 22% of commits
13.5/13.5Contributor breadth — 97 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor4
contributors_sampled97
top_contributor_share0.217
How it's scored
40.9/42Issue resolution — 97% of issues closed
24.4/30PR acceptance — 3,464/4,255 decided PRs merged
3.7/13Newcomer PR acceptance — 2/7 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs3,464
open_issues59
closed_issues2,137
prs_merged_7d2
prs_decided_7d3
prs_merged_30d6
prs_decided_30d11
issue_closed_ratio0.973
closed_unmerged_prs791
first_time_authors_30d7
first_time_prs_merged_30d2
first_time_prs_decided_30d7
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
22.3/25Owner reach — 1,279 followers of fastify
25/25Track record — 140 public repos, account ~9 yr old
Inputs used
followers1,279
owner_typeOrganization
is_verifiedyes
owner_loginfastify
public_repos140
account_age_days3,541

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 0 days ago
20/20Version history — 331 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesfastify
ecosystemsnpm
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

89Excellent · 19% of overall
How it's scored
24/24CI workflows — 20 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.fastify.dev
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicswebframework, performance, speed, nodejs, hacktoberfest, fastify, fastify-core
has_wikino
homepagehttps://www.fastify.dev
docs_sitehttps://www.fastify.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

73Good · 16% of overall
How it's scored
30/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestspackage.json
has_codeql_workflowno
has_security_policyyes
has_dependabot_configyes
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

67Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://www.fastify.dev/llms.txt)
40/40Legible commit history — 77 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.fastify.dev/llms.txt
legible_history_share0.811
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — test/types/tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 5 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstest/types/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.05
How it's scored
27/45Type-checkable code — JavaScript with type-check config (test/types/tsconfig.json)
54.8/55Manageable file sizes — 1/296 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes96,058
source_files_sampled296
oversized_source_files1
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
Inputs used
example_dirsexamples
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

37,145GitHub stars
97contributors
352commits, last 12 months
0days since last push
100releases
4bus factor
59open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index npm:fastify@5.12.5; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 3,018 ⇿
0Stars
3,018Forks
47Releases

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.

2,0002,2002,4002,6002,8003,0003,2003,018422024-042025-062026-09
Major 1Minor 15Patch 24

Each point covers 3 days.

Direct dependencies 15
RegistryPackageVersion constraintManifest
npm@fastify/ajv-compiler^4.0.5package.json
npm@fastify/error^4.0.0package.json
npm@fastify/fast-json-stringify-compiler^5.0.0package.json
npm@fastify/proxy-addr^5.0.0package.json
npmabstract-logging^2.0.1package.json
npmavvio^9.0.0package.json
npmfast-json-stringify^7.0.0package.json
npmfind-my-way^9.6.0package.json
npmlight-my-request^6.0.0package.json
npmpino^9.14.0 || ^10.1.0package.json
npmprocess-warning^5.1.0package.json
npmrfdc^1.3.1package.json
npmsecure-json-parse^4.0.0package.json
npmsemver^7.6.0package.json
npmtoad-cache^3.7.0package.json
All dependencies 53

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

RegistryPackageVersionRelation
npm@fastify/ajv-compiler^4.0.5direct
npm@fastify/error^4.0.0direct
npm@fastify/fast-json-stringify-compiler^5.0.0direct
npm@fastify/proxy-addr^5.0.0direct
npmabstract-logging^2.0.1direct
npmavvio^9.0.0direct
npmfast-json-stringify^7.0.0direct
npmfind-my-way^9.6.0direct
npmlight-my-request^6.0.0direct
npmpino^9.14.0 || ^10.1.0direct
npmprocess-warning^5.1.0direct
npmrfdc^1.3.1direct
npmsecure-json-parse^4.0.0direct
npmsemver^7.6.0direct
npmtoad-cache^3.7.0direct
npm@jsumners/line-reporter^1.0.1indirect
npm@stylistic/eslint-plugin^5.1.0indirect
npm@stylistic/eslint-plugin-js^4.1.0indirect
npm@types/node^26.0.1indirect
npmajv^8.12.0indirect
npmajv-errors^3.0.0indirect
npmajv-formats^3.0.1indirect
npmajv-i18n^4.2.0indirect
npmajv-merge-patch^5.0.1indirect
npmautocannon^8.0.0indirect
npmborp^1.0.0indirect
npmbranch-comparer^1.1.0indirect
npmconcurrently^10.0.0indirect
npmcross-env^10.0.0indirect
npmesbuild^0.28.1indirect
npmeslint^9.0.0indirect
npmfast-json-body^1.1.0indirect
npmfastify-plugin^6.0.0indirect
npmfastify-tsconfig^3.0.0indirect
npmfluent-json-schema^6.0.0indirect
npmh2url^0.2.0indirect
npmhttp-errors^2.0.0indirect
npmjoi^18.0.1indirect
npmjson-schema-to-ts^3.0.1indirect
npmJSONStream^1.3.5indirect
npmmarkdownlint-cli2^0.23.0indirect
npmneostandard^0.12.0indirect
npmnode-forge^1.3.1indirect
npmproxyquire^2.1.3indirect
npmsplit2^4.2.0indirect
npmtstyche^7.0.0indirect
npmtypebox^1.0.81indirect
npmtypescript~6.0.2indirect
npmundici^8.0.0indirect
npmvary^1.1.2indirect
npmwebpack^5.49.0indirect
npmwebpack-cli^4.7.2indirect
npmyup^1.4.0indirect
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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.