GitHub Trending
fmtlib/fmt
A modern formatting library
Current momentum
Stars
25.9K
+0 since sync
Commits
10
in period
Active contributors
4
+0%
Issues closed
4
1034.4h 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
10 commits · 10 opened PRs · 4 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 breadth16.1 / 25 pts
4 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 resolution3.0 / 20 pts
1034.4 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 cadence0.0 / 15 pts
67 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…
3.1K forks
Downstream adoption
16 open issues
Community demand
67 day cadence
Shipping consistency