Developer infrastructure
nodejs/node
Node.js JavaScript runtime β¨π’πβ¨
Current momentum
Stars
122.5K
+133 since sync
Commits
76
in period
Active contributors
29
+0%
Issues closed
3
1555.2h avg. resolution
Recorded trajectory
Movement you can verify over time.
Loading daily momentum history.
Behind the number
A score you can inspect.
Each signal contributes points to the total. These are capped GitHub samples, not complete activity counts or proof of adoption.
Development activity40.0 / 40 pts
76 commits Β· 35 opened PRs Β· 3 closed issues in 7 days
24 + 22 Γ ln(1 + weekly weighted activity). Activity = commits + 2 Γ opened PRs + closed issues. Signal bounded to 0β100, then weighted 40%.
Contributor breadth25.0 / 25 pts
29 sampled contributors in 7 days Β· 0% contributor-growth input
24 + 25 Γ ln(1 + contributors Γ β(7 / days)) + 0.15 Γ growth. Growth uses the 30-day windows; capped samples use a neutral 0 input. Signal bounded to 0β100, then weighted 25%.
Issue resolution1.9 / 20 pts
1555.2 hours resolution input
105 β 9 Γ logβ(1 + hours). Uses sampled closed issues, not first-response time. With no resolved issues, the model uses 168 hours. Signal bounded to 0β100, then weighted 20%.
Release cadence12.8 / 15 pts
4 days cadence input
105 β 5 Γ cadence days. With fewer than two published releases, the model uses time since the last push as a proxy. Signal bounded to 0β100, then weighted 15%.
What changed in the recorded sample?
Loading recorded observationsβ¦
40.3K forks
Downstream adoption
1.2K open issues
Community demand
4 day cadence
Shipping consistency