How the verdict was reached
read September 13, 2026 from the GitHub API for TabbyML/tabby| Signal | Value | Effect | Why |
|---|---|---|---|
| Base | 100 | 100 | Every row starts at 100, and the effects below move it. |
| Last commit | 2 months ago, June 30, 2026 | -28 | Last push 74 days ago. The commit line has slowed. |
| Commits, 90 days | 1 | none | Only 1 commit in the last 12 weeks. Too few to earn the volume credit. |
| Last release | next-alpha, 7 months ago | -12 | Last release 215 days ago against a 7-day cadence. Over three times its own gap. |
| Release cadence | 7 days, median | not scored | |
| Issue response | too few issues to sample | none | Not enough recent issues to measure a response time. |
| Unanswered issues | 100% of 8 sampled | -8 | 100% of the recent issues sampled have no maintainer reply at all. |
| Committers, 90 days | 1 | -5 | One person has committed in the last 90 days. Single point of failure. |
| Bus factor | 1 | not scored | |
| Archived | no | not scored | |
| Licence | none declared | -6 | No license file. Legally unsafe to depend on regardless of activity. |
| Freshness | 41/100 | 41 | 26 to 64 is slowing. |