bvaughn/react-virtualized
React components for efficiently rendering large lists and tabular data
27.1k stars · 3k forks · JavaScript
At risk
At risk: no human commits in a year.
Why
- No human commits since January 2025, and 3 of 8 recent issues got a maintainer reply. (source 1, source 2, source 3, source 4)
- Maintainers took a median of 59 days to first respond to 8 recent issues. (source 1, source 2, source 3, source 4)
What would change this
- A release or merged commit from a maintainer.
- Maintainers reply faster, with a median under 30 days.
Maintenance
CompleteDormant
- Human commits, 30 days
- 0
- Human commits, 90 days
- 0
- Human commits, 365 days
- 0
- Bot share of commits, 365 days
- 0%
- Last commit
- Jan 20, 2025 (1 year ago)
- Last human commit
- Jan 20, 2025 (1 year ago)
- Authors, 90 days
- 0
- Last release
- Jan 20, 2025 (1 year ago)
- Median PR merge time
- 5 days
Responsiveness: of 8 recent issues, 38% got a maintainer reply. Median first response: 59 days.
- No human commits in 365 days, and most issues go unanswered.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Personal account
- Commits sampled
- 69 since May 8, 2019
- Authors for half of commits
- 2
- Authors for 80% of commits
- 19
- Contributors
- 182
Top committers
- wuweiweiwu: 41% of commits
- bvaughn: 10% of commits
- Hypnosphi: 3% of commits
- inokawa: 3% of commits
- Jun Kokatsu: 3% of commits
- No human commits in the last 365 days, so shares use the newest 100 commits back to 2019-05-08T07:55:22Z.
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
Bursts
- Dec 12, 2015 to Dec 16, 2015: about 346 more stars than usual, peak 138 in one day, a spike that tapers off. We couldn't check for an outside explanation.
- Jan 30, 2016 to Feb 5, 2016: about 155 more stars than usual, peak 51 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Feb 15, 2016 to Feb 16, 2016: about 91 more stars than usual, peak 52 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Apr 2, 2016 to Apr 7, 2016: about 367 more stars than usual, peak 112 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- May 30, 2016 to Jun 2, 2016: about 266 more stars than usual, peak 124 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Oct 7, 2016 to Oct 7, 2016: about 33 more stars than usual, peak 40 in one day, a spike that tapers off. Outside explanation: a Hacker News post, a jump in forks.
- Nov 24, 2016 to Nov 25, 2016: about 45 more stars than usual, peak 39 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Apr 4, 2017 to Apr 5, 2017: about 64 more stars than usual, peak 63 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Dec 24, 2018 to Dec 24, 2018: about 63 more stars than usual, peak 77 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- 1 stars GitHub has since removed (tracked since Oct 14, 2026).
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- The star history looks organic.
Sources: How star history is analyzed
Risk
CompleteFlags
- Info: The OpenSSF Scorecard for this project is 3.1 out of 10 (deps.dev). Details
License
- Now
- MIT (OSI-approved)
- A year ago
- MIT (OSI-approved)
Packages
- react-virtualized (NPM): latest 9.22.6, published Jan 20, 2025
Advisories for the latest version: none listed
Package and advisory data: deps.dev and OSV.
OpenSSF Scorecard: 3.1 out of 10 (via deps.dev).
Sources: GitHub: bvaughn/react-virtualized, deps.dev: npm react-virtualized
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/bvaughn/react-virtualized)Earlier verdicts
- Oct 14, 2026: At risk
- Oct 14, 2026: At risk
Computed 9 hours ago · method 2026.10.2