How One API scored a D.

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.

30/100

GitHub credibility score

code
24/100
- ✓ Contributors & bus-factor: 9 recent contributors — concentrated
- ↓ Commit recency: last commit 566d ago
- ↓ Commit cadence: 0 commits in 90 days
- ✓ Issue close ratio: 49% of issues closed
- ↓ Release cadence: 0 releases in 12 months
- ✓ Stars (log-damped): 36,840 stars (log-damped)
- – Star authenticity: star-velocity check unavailable — GitHub no longer publishes stargazer timestamps for this repo
- – Dependent repos: not measurable — no package listing on a registry we can query
identity
Not measured
- – Identity: no verified provenance yet
audits
Not measured
- – Third-party scans: not measurable — no registry listings for this tool
freshness
0/100
- ↓ Last shipped: last commit 566d ago — standard-churn tools are expected to ship about every 120d
community
100/100
- – Recommends: no recommends from gate-passing builders yet
- ✓ Hacker News mentions: 27 Hacker News stories pointing at this tool

Components that could not be measured are left out of the average entirely, and their weight is redistributed, never scored as zero. Identity and Community are left out the same way when they would not have raised the score. How scores are calculated.