Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 18:51 UTC

react-component / virtual-list

📜 Virtual scrolling list component for React.

TypeScript · JavaScriptMIT★ 815 stars⑂ 171 forkssince Jul 2019View on GitHub ↗
KindLibraryNetwork servicehow this is determined

react-component/virtual-list holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (88/100) and lowest on AI Readiness (54/100). It was last updated 24 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

react-componentOrganization
2,350 followers111 public repossince Oct 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@rc-component/virtual-list1.5.14,939,9431127 days agoreactreact-componentvirtual-list

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
28.8/36Push recencylast push 24 days ago
6.2/36Commit cadence9/52 weeks with commits
14.3/18Commit volume38 commits in the last year
10/10OpenSSF Scorecard: Maintained17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year38
human_commit_share0.92
days_since_last_push24
active_weeks_last_year9

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 27 days ago
27/27Release cadencea release every ~26.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tag@rc-component/virtual-list@1.5.1
releases_from_tagsno
days_since_latest_release27
mean_days_between_releases26.9
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?

70Good · 17% of overall
How it's scored
47.2/60Stars815 stars
18.6/25Forks171 forks
2.7/15Watchers4 watchers
Inputs used
forks171
stars815
watchers4
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
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads4,939,943 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@rc-component/virtual-list
dependents
ecosystemsnpm
total_downloads
monthly_downloads4,939,943
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.5/22.5Commit distributiontop contributor authored 80% of commits
13.5/13.5Contributor breadth31 contributors
10/10OpenSSF Scorecard: Contributorsproject has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled31
top_contributor_share0.799
How it's scored
12.1/42Issue resolution29% of issues closed
13.9/30PR acceptance132/285 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 5/28 approved changesets -- score normalized to 1
Inputs used
merged_prs132
open_issues54
closed_issues22
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.289
closed_unmerged_prs153
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
24.2/25Owner reach2,350 followers of react-component
25/25Track record111 public repos, account ~11 yr old
Inputs used
followers2,350
owner_typeOrganization
is_verifiedno
owner_loginreact-component
public_repos111
account_age_days4,320

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 27 days ago
20/20Version history11 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@rc-component/virtual-list
ecosystemsnpm
any_deprecatedno
min_days_since_publish27

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests12 out of 14 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://react-component.github.io/virtual-list
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsantd, react, react-component, ant-design, javascript
has_wikiyes
homepagehttps://react-component.github.io/virtual-list
docs_sitehttps://react-component.github.io/virtual-list
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

72Good · 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
2/2.5CI-Tests12 out of 14 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 5/28 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 9 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.5Maintained17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
2/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
4.5/5SASTSAST tool detected but not run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
6/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.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_packages6
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:@rc-component/virtual-list@1.5.1 runtime dependency closure — what installing the published package pulls in — 6 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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
35.4/40Legible commit history61 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.663
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.mjs
11/11Static type checkingtsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance8 of the last 100 commits are automated dependency updates
4/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.08
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/44 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes25,673
source_files_sampled44
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

815GitHub stars
31contributors
38commits, last 12 months
24days since last push
100releases
1bus factor
54open 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 ★ / 171 ⇿
0Stars
171Forks
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.

0408012016020017042019-082023-022026-08
Major 0Minor 17Patch 70

Each point covers 7 days.

OpenSSF Scorecard 6.5 / 10
6.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-27 18:51 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests12 out of 14 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/28 approved changesets -- score normalized to 1
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
9SASTSAST tool detected but not run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
8Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npm@babel/runtime^8.0.0package.json
npm@rc-component/resize-observer^1.0.1package.json
npm@rc-component/util^1.4.0package.json
npmclsx^2.1.1package.json
All dependencies 36

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

RegistryPackageVersionRelation
npm@babel/runtime^8.0.0direct
npm@rc-component/resize-observer^1.0.1direct
npm@rc-component/util^1.4.0direct
npmclsx^2.1.1direct
npm@eslint/compat^2.1.0indirect
npm@eslint/js^10.0.1indirect
npm@rc-component/father-plugin^2.2.0indirect
npm@rc-component/np^1.0.4indirect
npm@testing-library/dom^10.4.1indirect
npm@testing-library/jest-dom^6.9.1indirect
npm@testing-library/react^16.3.2indirect
npm@types/jest^30.0.0indirect
npm@types/node^26.0.1indirect
npm@types/react^19.2.17indirect
npm@types/react-dom^19.2.3indirect
npm@types/warning^3.0.4indirect
npmcross-env^10.1.0indirect
npmdumi^2.4.38indirect
npmeslint^10.6.0indirect
npmeslint-config-prettier^10.1.8indirect
npmeslint-plugin-jest^29.15.4indirect
npmeslint-plugin-react^7.37.5indirect
npmeslint-plugin-react-hooks^7.1.1indirect
npmfather^4.6.24indirect
npmgh-pages^6.3.0indirect
npmglob^13.0.6indirect
npmglobals^17.7.0indirect
npmhusky^9.1.7indirect
npmlint-staged^17.0.8indirect
npmprettier^3.9.4indirect
npmrc-animate^3.1.1indirect
npmrc-test^7.1.3indirect
npmreact^19.2.7indirect
npmreact-dom^19.2.7indirect
npmtypescript^6.0.3indirect
npmtypescript-eslint^8.62.1indirect
Dependency advisories 0

Installing npm:@rc-component/virtual-list@1.5.1 pulls in 6 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 statisticsnpm.