← Tambo
How Tambo scored an A.
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.
A
87/100
GitHub credibility score
code
81/100- ✓ Contributors & bus-factor: 8 recent contributors
- ✓ Commit recency: last commit 34d ago
- ✓ Commit cadence: 69 commits in 90 days
- ✓ Issue close ratio: 89% of issues closed
- ✓ Release cadence: 100 releases in 12 months
- ✓ Stars (log-damped): 11,177 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 commit 34d ago — standard-churn tools are expected to ship about every 120d
community
59/100- – Recommends: no recommends from gate-passing builders yet
- ✓ Hacker News mentions: 5 Hacker News stories pointing at this tool
Community did not lower this score. Community can only ever add. It did not raise the average for Tambo, so the score shown is the one it would have without it. The component is still listed above, with its real value.
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.