Stars Measure Popularity. Contributor Density Measures Survival.
GitHub stars are the metric most commonly cited when evaluating framework health. React leads with 246,094 stars. Angular follows at 100,443. Next.js sits at 140,229. But stars measure one thing only: how many developers clicked a button. They do not measure how many developers are actively maintaining the codebase, fixing vulnerabilities, reviewing pull requests, and shipping releases.
WebPulse introduces a different metric: contributor density — the number of active contributors per 100,000 GitHub stars. This ratio strips away popularity and exposes the engineering foundation beneath it. The results reorder the framework hierarchy.
The Frameworks With the Deepest Bench
When ranked by contributor density, the leaderboard shifts dramatically. HTMX leads with 923 contributors per 100K stars — its 48,239 stars are backed by 445 active contributors. SvelteKit follows at 2,192 per 100K stars, though its near-zero commit velocity complicates that signal. Among frameworks with healthy commit activity, the leaders are revealing.
Laravel: 1,078 per 100K stars (375 contributors, 34,790 stars). Remix: 1,374 per 100K stars (455 contributors, 33,121 stars). Joomla: 5,554 per 100K stars (283 contributors, 5,095 stars). These frameworks have contributor bases that are large relative to their popularity — meaning a higher percentage of their community is actively contributing, not just watching.
The Frameworks Running on Reputation
At the bottom of the contributor density ranking sit frameworks where popularity has outstripped engineering capacity. Gatsby has 742 per 100K stars — seemingly healthy, until you note its 179 annual commits and 4 releases. The contributors exist in name; the work has stopped. WordPress sits at 424 per 100K stars, with only 90 contributors maintaining a platform that runs 40% of the web.
React's 167 per 100K stars is the number that should concern enterprise architects. React is the most popular JavaScript framework by a wide margin. Its contributor base is one of the smallest relative to that popularity. Meta maintains a core team, but the ratio means that React's ecosystem health depends on a narrower engineering base than its adoption would suggest. Angular, backed by Google's dedicated team, achieves 2.2x React's density at 374 per 100K stars.
Angular's 3,950 Commits Complete the Picture
Contributor density alone does not prove sustainability. A framework could have high density but low output. Angular eliminates that concern. Its 376 contributors produce 3,950 commits per year and 50 releases — placing it among the top five frameworks by both commit velocity and release cadence. The combination of high contributor density and high output velocity is the signature of a sustainably engineered project.
React's 411 contributors produce 1,042 commits and 25 releases. Per contributor, that is 2.5 commits per year — compared to Angular's 10.5. Angular contributors are four times as productive by commit output. This is not a criticism of React's contributors; it reflects the organizational model. Angular's Google-backed team operates with the cadence of an enterprise software product. React's Meta-backed model is leaner by design, but that leanness translates to lower throughput per unit of community.
What This Means for Framework Selection
When a CTO asks whether a framework will be maintained in five years, star count is the wrong metric. Contributor density — combined with commit velocity and release cadence — answers that question with data. Angular's numbers describe a framework with deep, active, well-organized engineering support. React's numbers describe a framework where extraordinary popularity has outpaced the engineering base that sustains it. Both frameworks will exist in five years. The question is which one will respond faster when the next critical vulnerability drops.
