Developer infrastructure
junegunn/fzf
:cherry_blossom: A command-line fuzzy finder
Current momentum
Stars
83.6K
+35 since sync
Commits
6
in period
Active contributors
3
+-25%
Issues closed
3
1760.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 activity34.0 / 40 pts
6 commits · 3 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 breadth13.7 / 25 pts
3 sampled contributors in 7 days · -25% 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.6 / 20 pts
1760.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
21 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…
5.6K forks
Downstream adoption
333 open issues
Community demand
21 day cadence
Shipping consistency