This is an early release preview. You may encounter bugs.
← NanoMuse

How NanoMuse scored a C.

A way.space signal summary built from public evidence. It is not a user rating, and not a safety certification. How scores are calculated.

01 / Breakdown

Derived from GitHub, not voted.

C
64/100

GitHub credibility score

  • ✓ Contributors & bus-factor: 2 recent contributors — concentrated
  • ✓ Commit recency: last commit 0d ago
  • ✓ Commit cadence: 2279 commits in 90 days
  • ✓ Issue close ratio: 15% of issues closed
  • ✓ Release cadence: 50 releases in 12 months
  • ✓ Stars (log-damped): 3,047 stars (log-damped)
  • – Star authenticity: star-velocity check unavailable — GitHub no longer publishes stargazer timestamps for this repo
  • ✓ Engagement-to-star ratio: healthy engagement (0.38 per star)
Quality signalMeasuredWeightPoints
Contributors & bus-factor2 recent contributors — concentrated20%+0
Commit recencylast commit 0d ago20%+20
Commit cadence2279 commits in 90 days15%+15
Issue close ratio15% of issues closed15%+2
Release cadence50 releases in 12 months15%+15
Stars (log-damped)3,047 stars (log-damped)15%+12
Quality subtotal (Q)100%64

Authenticity multiplier (A)

× 1.00
  • – Star authenticity: star-velocity check unavailable — GitHub no longer publishes stargazer timestamps for this repo
  • ✓ Engagement-to-star ratio: healthy engagement (0.38 per star)

Quality 64 × authenticity 1.00 = 64/100

Quality signals add up to the subtotal, then the authenticity multiplier discounts bought-star and bot-stargazer patterns. How scores are calculated.