Menu

Rescored Sep 13, 2026, 06:20 UTC

Rescored nightly from the GitHub API

Rescored nightly from the GitHub APIRescored Sep 13, 2026, 06:20 UTCOpen API
345 tools tracked27 dead, 9 archived19 slowing299 maintained82 named by hand, 263 found by 9 topic searches29 changed verdict since August 1, 2026Frozen September 13, 2026

TabbySlowing

Self-hosted completion and chat server with IDE clients.

Is it still shipping?

Barely. Tabby is still open but slowing down. The last commit was 2 months ago, and it scores 41/100.

freshness 41/100
Every night it was read41 nightly readings, August 1, 2026 to September 13, 2026. Bar height is freshness out of 100; the ink is the verdict that night.
August 1, 2026September 13, 2026
The record

How the verdict was reached

read September 13, 2026 from the GitHub API for TabbyML/tabby
Every signal behind Tabby's verdict, and what each one moved the score by
SignalValueEffectWhy
Base100100Every row starts at 100, and the effects below move it.
Last commit2 months ago, June 30, 2026-28Last push 74 days ago. The commit line has slowed.
Commits, 90 days1noneOnly 1 commit in the last 12 weeks. Too few to earn the volume credit.
Last releasenext-alpha, 7 months ago-12Last release 215 days ago against a 7-day cadence. Over three times its own gap.
Release cadence7 days, mediannot scored
Issue responsetoo few issues to samplenoneNot enough recent issues to measure a response time.
Unanswered issues100% of 8 sampled-8100% of the recent issues sampled have no maintainer reply at all.
Committers, 90 days1-5One person has committed in the last 90 days. Single point of failure.
Bus factor1not scored
Archivednonot scored
Licencenone declared-6No license file. Legally unsafe to depend on regardless of activity.
Freshness41/1004126 to 64 is slowing.