Yes, and it just launched. xiaojilele-glitch/WhyBuddy appeared on beam June 10, 2026 and is too new to call yet. Current velocity score: 0.0/10.
New means the repo recently entered beam’s tracked set. Too little history exists to assign a momentum class yet; check back as more snapshots accumulate. Full methodology →
Yes, and it just launched. xiaojilele-glitch/WhyBuddy appeared on beam June 10, 2026 and is too new to call yet. Current velocity score: 0.0/10.
Beam classifies xiaojilele-glitch/WhyBuddy as new with a velocity score of 0.0/10. Beam fuses code activity, package adoption, sentiment, research citation, and production signals into a single 0–10 score; the classification thresholds are explained on /about.
The most recent commit to xiaojilele-glitch/WhyBuddy was today (June 10, 2026).
Beam refreshes xiaojilele-glitch/WhyBuddy's velocity score and class daily. The live tool profile is at /tools/95724; the JSON API endpoint is /api/v1/tools/95724.
