Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-23 08:20 UTC

rolldown / tsdown

The elegant bundler for libraries powered by Rolldown

TypeScriptMIT★ 4,278 stars⑂ 192 forkssince Mar 2024View on GitHub ↗
KindLibraryCommand-line toolNetwork servicehow this is determined

rolldown/tsdown holds a health index of 97 out of 100, placing it in the Exceptional band. It scores highest on Vitality (100/100) and lowest on Sustainability & Governance (72/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

RolldownOrganization · verified domain
791 followers26 public repossince Nov 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmtsdown0.23.018,650,69520819 days ago

Metrics by category

Vitality

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

100Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recency — last push 0 days ago
36/36Commit cadence — 52/52 weeks with commits
18/18Commit volume — 640 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year640
human_commit_share0.97
days_since_last_push0
active_weeks_last_year52

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 19 days ago
27/27Release cadence — a release every ~5.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv0.23.0
releases_from_tagsno
days_since_latest_release19
mean_days_between_releases5.1
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?

84Excellent · 17% of overall
How it's scored
58.9/60Stars — 4,278 stars
19/25Forks — 192 forks
5.8/15Watchers — 12 watchers
Inputs used
forks192
stars4,278
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/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_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 18,650,695 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestsdown
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads18,650,695
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?

72Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.3/22.5Commit distribution — top contributor authored 85% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 39 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled98
top_contributor_share0.852
How it's scored
38.9/42Issue resolution — 93% of issues closed
24.8/30PR acceptance — 344/416 decided PRs merged
8.1/13Newcomer PR acceptance — 5/8 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 7/28 approved changesets -- score normalized to 2
Inputs used
merged_prs344
open_issues39
closed_issues486
prs_merged_7d0
prs_decided_7d0
prs_merged_30d7
prs_decided_30d10
issue_closed_ratio0.926
closed_unmerged_prs72
first_time_authors_30d7
first_time_prs_merged_30d5
first_time_prs_decided_30d8
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
20.8/25Owner reach — 791 followers of rolldown
20.1/25Track record — 26 public repos, account ~4 yr old
Inputs used
followers791
owner_typeOrganization
is_verifiedyes
owner_loginrolldown
public_repos26
account_age_days1,764

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows — 11 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js, package.json ("prettier")
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 10 out of 10 merged PRs checked by a CI test -- score normalized to 10
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://tsdown.dev
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicslibrary, oxc, rolldown, typescript, bundler
has_wikino
homepagehttps://tsdown.dev
docs_sitehttps://tsdown.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

80Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 7/28 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 39 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
6/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.5
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 advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages66
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:tsdown@0.23.0 runtime dependency closure — what installing the published package pulls in — 66 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.

82Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://tsdown.dev/llms.txt)
40/40Legible commit history — 97 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://tsdown.dev/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes10,286
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js, package.json ("prettier")
11/11Static type checking — docs/tsconfig.json, tests/fixtures/issue-206/packages/pkg1/tsconfig.json, tests/fixtures/issue-206/packages/pkg2/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 3 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsdocs/tsconfig.json, tests/fixtures/issue-206/packages/pkg1/tsconfig.json, tests/fixtures/issue-206/packages/pkg2/tsconfig.json, tsconfig.json
agent_commit_share0.03
toolchain_manifests—
dependency_bot_commit_share0.03
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.6/55Manageable file sizes — 1/145 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes64,242
source_files_sampled145
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — recipes
Inputs used
example_dirsrecipes
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

4,278GitHub stars
98contributors
640commits, last 12 months
0days since last push
100releases
1bus factor
39open 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 ★ / 192 ⇿
0Stars
192Forks
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.

0408012016020019182024-062025-082026-09
Major 0Minor 10Patch 62

Each point covers 3 days.

OpenSSF Scorecard 7.5 / 10
7.5aggregate

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-23 08:20 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 7/28 approved changesets -- score normalized to 2
10Contributorsproject has 39 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
8Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
npmcaccatalog:prodpackage.json
npmdefucatalog:prodpackage.json
npmempathiccatalog:prodpackage.json
npmhookablecatalog:prodpackage.json
npmimport-without-cachecatalog:prodpackage.json
npmobugcatalog:prodpackage.json
npmpicomatchcatalog:prodpackage.json
npmrolldowncatalog:prodpackage.json
npmrolldown-plugin-dtscatalog:prodpackage.json
npmtinyexeccatalog:prodpackage.json
npmtinyglobbycatalog:prodpackage.json
npmtree-killcatalog:prodpackage.json
npmunconfig-corecatalog:prodpackage.json
npmverkitcatalog:prodpackage.json
All dependencies 44

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

RegistryPackageVersionRelation
npmcaccatalog:proddirect
npmobugcatalog:proddirect
npmrolldowncatalog:proddirect
npmtinyexeccatalog:proddirect
npmtinyglobbycatalog:proddirect
npmverkitcatalog:proddirect
npm@antfu/nicatalog:migrateindirect
npm@ast-grep/napicatalog:migrateindirect
npm@clack/promptscatalog:createindirect
npm@iconify-json/logoscatalog:docsindirect
npm@pnpm/exe.android-arm6412.5.0indirect
npm@pnpm/exe.android-x6412.5.0indirect
npm@pnpm/exe.darwin-arm6412.5.0indirect
npm@pnpm/exe.darwin-x6412.5.0indirect
npm@pnpm/exe.freebsd-x6412.5.0indirect
npm@pnpm/exe.linux-arm6412.5.0indirect
npm@pnpm/exe.linux-arm64-musl12.5.0indirect
npm@pnpm/exe.linux-ppc6412.5.0indirect
npm@pnpm/exe.linux-riscv6412.5.0indirect
npm@pnpm/exe.linux-s390x12.5.0indirect
npm@pnpm/exe.linux-x6412.5.0indirect
npm@pnpm/exe.linux-x64-musl12.5.0indirect
npm@pnpm/exe.win32-arm6412.5.0indirect
npm@pnpm/exe.win32-x6412.5.0indirect
npm@shikijs/vitepress-twoslashcatalog:docsindirect
npm@vueuse/corecatalog:docsindirect
npmconsolacatalog:migrateindirect
npmdiffcatalog:migrateindirect
npmgigetcatalog:createindirect
npmlightningcsscatalog:prodindirect
npmoxc-minifycatalog:docsindirect
npmpackage-manager-detectorcatalog:prodindirect
npmpnpm12.5.0indirect
npmpostcss-load-configcatalog:prodindirect
npmtypedoccatalog:docsindirect
npmtypedoc-plugin-markdowncatalog:docsindirect
npmtypedoc-vitepress-themecatalog:docsindirect
npmvitecatalog:docsindirect
npmvitepresscatalog:docsindirect
npmvitepress-plugin-group-iconscatalog:docsindirect
npmvitepress-plugin-llmscatalog:docsindirect
npmvoidcatalog:docsindirect
npmvuecatalog:docsindirect
npmvue-tsccatalog:docsindirect
Dependency advisories 0

Installing npm:tsdown@0.23.0 pulls in 66 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.34.0 — full methodology · metrics wiki.

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