How Tinyagentos scored a B.

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.

76/100

GitHub credibility score

code
66/100
- ↓ Contributors & bus-factor: 1 recent contributor — concentrated
- ✓ Commit recency: last commit 0d ago
- ✓ Commit cadence: 3311 commits in 90 days
- ✓ Issue close ratio: 46% of issues closed
- ✓ Release cadence: 52 releases in 12 months
- ✓ Stars (log-damped): 519 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: not yet active — activates with verified publisher claims
audits
Not measured
- – Third-party scans: no third-party scan data from listed registries
freshness
100/100
- ✓ Last shipped: last release 0d ago — standard-churn platforms are expected to ship about every 120d
community
Not measured
- – Community: no community signal yet — nobody has recommended it, posted about it, or shared it on Hacker News

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.