Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-04 18:12 UTC

rolldown / plugins

Official Rolldown plugins

TypeScriptMIT★ 17 stars⑂ 5 forkssince Feb 2026View on GitHub ↗

rolldown/plugins holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (86/100) and lowest on Engineering Quality (57/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

RolldownOrganization
788 followers26 public repossince Nov 2021

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

Package ecosystems

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
13.2/36Commit cadence19/52 weeks with commits
18/18Commit volume147 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year147
human_commit_share0.53
days_since_last_push1
active_weeks_last_year19

Release discipline

100Exceptional
How it's scored
27/27Ships releases31 releases published
36/36Release recencylatest release 29 days ago
27/27Release cadencea release every ~8.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count31
latest_release_tagplugin-styled-jsx@0.1.3
releases_from_tagsno
days_since_latest_release29
mean_days_between_releases8.6
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?

60Moderate · 17% of overall
How it's scored
19.5/60Stars17 stars
5/25Forks5 forks
0/15Watchers1 watchers
Inputs used
forks5
stars17
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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 downloads592,553,490 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@rolldown/plugin-babel, @rolldown/plugin-emotion, @rolldown/plugin-styled-jsx, @rolldown/pluginutils, @rolldown/plugin-transform-imports, @rolldown/plugin-jsx-remove-attributes, oxc-unshadowed-visitor
dependents
ecosystemsnpm
total_downloads
monthly_downloads592,553,490
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?

69Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.4/22.5Commit distributiontop contributor authored 94% of commits
8.1/13.5Contributor breadth6 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.938
How it's scored
34.4/42Issue resolution82% of issues closed
27.4/30PR acceptance95/104 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 1/8 approved changesets -- score normalized to 1
Inputs used
merged_prs95
open_issues2
closed_issues9
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.818
closed_unmerged_prs9
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
20.8/25Owner reach788 followers of rolldown
19.8/25Track record26 public repos, account ~4 yr old
Inputs used
followers788
owner_typeOrganization
is_verified
owner_loginrolldown
public_repos26
account_age_days1,714
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable7 package(s) on npm
35/35Publish recencylatest publish 29 days ago
20/20Version history124 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@rolldown/plugin-babel, @rolldown/plugin-emotion, @rolldown/plugin-styled-jsx, @rolldown/pluginutils, @rolldown/plugin-transform-imports, @rolldown/plugin-jsx-remove-attributes, oxc-unshadowed-visitor
ecosystemsnpm
any_deprecatedno
min_days_since_publish29

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests25 out of 25 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
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-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests25 out of 25 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 1/8 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 5 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
7.5/7.5Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
6/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.5
Excluded from scoring (no data or not applicable): Packaging, 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_packages1
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:@rolldown/plugin-babel@0.2.3 runtime dependency closure — what installing the published package pulls in — 1 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.

67Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history53 of 53 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingexamples/tsconfig.json, tsconfig.json
10/10Reproducible environmentlockfile
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance47 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsexamples/tsconfig.json, tsconfig.json
agent_commit_share0.02
toolchain_manifests
dependency_bot_commit_share0.47
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/528 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes35,438
source_files_sampled528
oversized_source_files0
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 examplesexamples
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

17GitHub stars
6contributors
147commits, last 12 months
1days since last push
31releases
1bus factor
2open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 5 ⇿
0Stars
5Forks
20Releases

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.

12345512026-032026-052026-07
Major 0Minor 0Patch 0
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-08-04 18:12 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests25 out of 25 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/8 approved changesets -- score normalized to 1
10Contributorsproject has 5 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 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
8Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 19
RegistryPackageVersion constraintManifest
npm@oxc-node/clicatalog:internal-packages/swc-output-gen/package.json
npm@rollup/plugin-swccatalog:internal-packages/swc-output-gen/package.json
npm@swc/corecatalog:internal-packages/swc-output-gen/package.json
npm@swc/plugin-emotioncatalog:internal-packages/swc-output-gen/package.json
npm@swc/plugin-react-remove-propertiescatalog:internal-packages/swc-output-gen/package.json
npm@swc/plugin-styled-jsxcatalog:internal-packages/swc-output-gen/package.json
npm@swc/plugin-transform-importscatalog:internal-packages/swc-output-gen/package.json
npmrolldowncatalog:internal-packages/swc-output-gen/package.json
npmtinyglobby^0.2.17internal-packages/swc-output-gen/package.json
npmpicomatch^4.0.5packages/babel/package.json
npm@emotion/hash^0.9.2packages/emotion/package.json
npm@jridgewell/gen-mapping^0.3.13packages/emotion/package.json
npmrolldown-string^0.3.1packages/emotion/package.json
npmrolldown-string^0.3.1packages/jsx-remove-attributes/package.json
npm@jridgewell/gen-mapping^0.3.13packages/styled-jsx/package.json
npmlightningcss^1.33.0packages/styled-jsx/package.json
npmoxc-walker^1.1.1packages/styled-jsx/package.json
npmrolldown-string^0.3.1packages/styled-jsx/package.json
npmrolldown-string^0.3.1packages/transform-imports/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 0

Installing npm:@rolldown/plugin-babel@0.2.3 pulls in 1 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.30.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.