Eugeny/tabby
First read
Visible and active, but adoption proof is still thinner
Eugeny/tabby has enough public attention and recent movement to stay on the shortlist, but package usage is still partial, so the next step should be source and ecosystem validation rather than a quick yes.
70.8K public stars in the current GitStar snapshot.
Recognizable in the ecosystem
Last commit Apr 24, 2026.
Fresh activity
Treat stars as discovery context until a linked package appears.
No linked package mapping
One or more key signals are partial, so GitStar keeps the interpretation conservative.
Partial snapshot
Snapshot facts
- 70.8K stars
- 4K forks
- Last commit Apr 24, 2026
- Package usage not mapped yet
Compare lens
ohmyzsh/ohmyzsh and microsoft/terminal are the closest comparison targets GitStar found. A side-by-side comparison usually tells you more than a single raw rank.
Signal trail
Trajectory
Read the recent motion first. This block is for deciding whether the repository still looks alive, compounding, or flattening before you trust stars alone.
Package reality
No linked npm or PyPI package is mapped for this repository yet, so the page leans more heavily on GitHub-visible popularity and should be read more conservatively.
GitStar expects a package signal here, but no npm or PyPI package is linked to this repository yet.
Validation note
GitStar can summarize public signals for Eugeny/tabby, but the GitHub repository is still the primary place to confirm release cadence, issue activity, and maintainer intent.
GitStar surfaces public popularity and package signals. These rankings are not endorsements, security reviews, or investment advice.
Why this rank
This repository stands out because it combines fresh update and stable visibility.
Reconstructed from current stars and cached daily/weekly/monthly deltas.
GitStar can see repository momentum, but it does not have a reliable linked package signal yet.
Treat stars and recent movement as discovery context only until npm or PyPI usage is available.
ohmyzsh/ohmyzsh
Overlaps on topics such as terminal, which makes it a stronger alternative than a random popularity neighbor.
microsoft/terminal
Overlaps on topics such as terminal, which makes it a stronger alternative than a random popularity neighbor.
vuejs/vue
Lives in the same TypeScript ecosystem, but should still be checked for actual use-case overlap before you treat it as a direct substitute.
microsoft/vscode
Lives in the same TypeScript ecosystem, but should still be checked for actual use-case overlap before you treat it as a direct substitute.
Cross-links
GitStar picked ohmyzsh + terminal as the closest next comparison from the related repository set.
Embed Badge
[](https://gitstar.space/repo/Eugeny/tabby)<a href="https://gitstar.space/repo/Eugeny/tabby"><img src="https://gitstar.space/api/badge/Eugeny/tabby" alt="GitStar"></a>🔗 Wider nearby ecosystem
🙃 A delightful community-driven (with 2,400+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool that makes it easy to keep up with the latest updates from the community.
The new Windows Terminal and the original Windows console host, all in the same place!
This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core
Visual Studio Code
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
Curated coding interview preparation materials for busy software engineers
Next step after the validation read
Learn and methodology
About This Page
This page provides a quick overview of Eugeny/tabby based on GitStar's cached data. The signal chart reconstructs approximate checkpoints from current stars plus cached daily, weekly, and monthly star deltas, so it is best read as directional context rather than as a precise historical audit log.
Want to show your project's ranking? Copy the badge embed code above and add it to your README.