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

elysiajs / elysia

Ergonomic Framework for Humans

TypeScriptMIT★ 18,840 stars⑂ 562 forkssince Dec 2022View on GitHub ↗

elysiajs/elysia holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (94/100) and lowest on Security (54/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

elysiaOrganization
806 followers30 public repossince Dec 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmelysia1.4.293,059,43574049 days agobunhttpwebserver

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recencylast push 5 days ago
22.8/36Commit cadence33/52 weeks with commits
18/18Commit volume579 commits in the last year
5/10OpenSSF Scorecard: Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year579
human_commit_share1
days_since_last_push5
active_weeks_last_year33

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 49 days ago
27/27Release cadencea release every ~18.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tag1.4.29
releases_from_tagsno
days_since_latest_release49
mean_days_between_releases18.3
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?

94Exceptional · 17% of overall
How it's scored
60/60Stars18,840 stars
22.9/25Forks562 forks
9.2/15Watchers46 watchers
Inputs used
forks562
stars18,840
watchers46
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
80/80Monthly downloads3,059,435 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageselysia
dependents
ecosystemsnpm
total_downloads
monthly_downloads3,059,435
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?

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.1/22.5Commit distributiontop contributor authored 86% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 18 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.864
How it's scored
33.2/42Issue resolution79% of issues closed
17.8/30PR acceptance207/348 decided PRs merged
0/13Newcomer PR acceptance0/4 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 8/23 approved changesets -- score normalized to 3
Inputs used
merged_prs207
open_issues274
closed_issues1,036
prs_merged_7d0
prs_decided_7d1
prs_merged_30d1
prs_decided_30d6
issue_closed_ratio0.791
closed_unmerged_prs141
first_time_authors_30d4
first_time_prs_merged_30d0
first_time_prs_decided_30d4
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
20.9/25Owner reach806 followers of elysiajs
18.2/25Track record30 public repos, account ~3 yr old
Inputs used
followers806
owner_typeOrganization
is_verified
owner_loginelysiajs
public_repos30
account_age_days1,339
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 49 days ago
20/20Version history740 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageselysia
ecosystemsnpm
any_deprecatedno
min_days_since_publish49

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests4 out of 8 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://elysiajs.com
10/10Repository description
10/10Topics6 topics
10/10Wiki
Inputs used
topicsframework, typescript, bun, web, http, server
has_wikiyes
homepagehttps://elysiajs.com
docs_sitehttps://elysiajs.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
1.2/2.5CI-Tests4 out of 8 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 8/23 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 18 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
3.8/7.5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities23 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages4
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:elysia@1.4.29 runtime dependency closure — what installing the published package pulls in — 4 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.

76Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
28.3/40Legible commit history53 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.53
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes2,834
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.json
11/11Static type checkingtest/cloudflare/tsconfig.json, tsconfig.json
10/10Reproducible environmentlockfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesbun.lockb, package-lock.json, pnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstest/cloudflare/tsconfig.json, tsconfig.json
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.1/55Manageable file sizes4/238 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes327,011
source_files_sampled238
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexample
Inputs used
example_dirsexample
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

18,840GitHub stars
99contributors
579commits, last 12 months
5days since last push
100releases
1bus factor
274open 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 ★ / 562 ⇿
0Stars
562Forks
100Releases

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.

0100200300400500600557172023-012024-102026-08
Major 0Minor 3Patch 91

Each point covers 4 days.

OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-05 05:01 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
5CI-Tests4 out of 8 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 8/23 approved changesets -- score normalized to 3
10Contributorsproject has 18 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities23 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npmcookie^1.1.1package.json
npmexact-mirror^0.2.7package.json
npmfast-decode-uri-component^1.0.1package.json
npmmemoirist^0.4.0package.json
All dependencies 81

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

RegistryPackageVersionRelation
npmcookie1.0.2direct
npmcookie^1.1.1direct
npmexact-mirror0.2.2direct
npmexact-mirror^0.2.7direct
npmfast-decode-uri-component1.0.1direct
npmfast-decode-uri-component^1.0.1direct
npmmemoirist^0.4.0direct
npm@cloudflare/kv-asset-handler0.4.0indirect
npm@cloudflare/unenv-preset2.7.4indirect
npm@cloudflare/workerd-darwin-arm641.20250924.0indirect
npm@cspotcode/source-map-support0.8.1indirect
npm@elysiajs/openapi^1.4.1indirect
npm@esbuild/darwin-arm640.25.4indirect
npm@img/sharp-darwin-arm640.33.5indirect
npm@img/sharp-libvips-darwin-arm641.0.4indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.9indirect
npm@poppinss/colors4.1.5indirect
npm@poppinss/dumper0.6.4indirect
npm@poppinss/exception1.2.2indirect
npm@sinclair/typebox0.34.41indirect
npm@sindresorhus/is7.1.0indirect
npm@speed-highlight/core1.2.7indirect
npm@types/bun^1.3.5indirect
npm@types/cookie1.0.0indirect
npm@types/fast-decode-uri-component^1.0.0indirect
npm@typescript-eslint/eslint-plugin^8.30.1indirect
npm@typescript-eslint/parser^8.30.1indirect
npmacorn8.14.0indirect
npmacorn-walk8.3.2indirect
npmarktype^2.1.22indirect
npmblake3-wasm2.1.5indirect
npmcolor4.2.3indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcolor-string1.9.1indirect
npmdefu6.1.4indirect
npmdetect-libc2.1.1indirect
npmelysia1.4.8indirect
npmerror-stack-parser-es1.0.5indirect
npmesbuild0.25.4indirect
npmesbuild-fix-imports-plugin^1.0.22indirect
npmeslint^9.24.0indirect
npmeslint-plugin-security^3.0.1indirect
npmeslint-plugin-sonarjs^3.0.2indirect
npmexit-hook2.2.1indirect
npmexpect-type^1.2.1indirect
npmexsolve1.0.7indirect
npmfile-type^20.4.1indirect
npmfsevents2.3.3indirect
npmglob-to-regexp0.4.1indirect
npmis-arrayish0.3.4indirect
npmkleur4.1.5indirect
npmknip^5.64.1indirect
npmmime3.0.0indirect
npmminiflare4.20250924.0indirect
npmohash2.0.11indirect
npmopenapi-types12.1.3indirect
npmpath-to-regexp6.3.0indirect
npmpathe2.0.3indirect
npmprettier^3.5.3indirect
npmsemver7.7.2indirect
npmsharp0.33.5indirect
npmsimple-swizzle0.2.4indirect
npmstoppable1.1.0indirect
npmsupports-color10.2.2indirect
npmtsup^8.4.0indirect
npmtypescript5.9.2indirect
npmtypescript^5.8.3indirect
npmufo1.6.1indirect
npmundici7.14.0indirect
npmunenv2.0.0-rc.21indirect
npmvalibot^1.1.0indirect
npmworkerd1.20250924.0indirect
npmwrangler4.40.2indirect
npmws8.18.0indirect
npmyouch4.1.0-beta.10indirect
npmyouch-core0.3.3indirect
npmzod3.22.3indirect
npmzod^4.1.5indirect
Dependency advisories 0

Installing npm:elysia@1.4.29 pulls in 4 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.

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