Trending by velocity
The trending board ranks repositories by velocity: how fast a project is gaining stars, forks, and activity over a recent window, rather than its all-time star count. A project published last week can therefore rank above a long-established one if it is rising faster right now. You can adjust the time window and filter by programming language and forge. Browse it on the trending page.
Gems are hand-picked
Above the automated board, our editors award gem status to standout projects: things that are genuinely useful, well-built, or simply interesting, independent of star count. This is editorial judgement, led by our curation team, not an automated threshold. A gem badge is not a guarantee of a project's quality, safety, or legality.
Showcase ownership is verified
Maintainers can list their own work in the showcase. To keep it honest, a submission stays hidden until ownership is verified by detecting the GitGem.org README badge in the live repository. The badge also adds a backlink, so the connection is visible from both the project and GitGem.org.
Spam and quality filtering
Every way a repository can enter GitGem.org runs the same spam scoring. Obvious spam is dropped automatically. When a single ambiguous signal fires, the repository goes to a human review queue instead of being silently blocked, so a real project flagged by one borderline keyword is not lost. Approved repositories are permanently whitelisted.
Frequently asked
How does GitGem.org decide what is trending?
Trending is ranked by velocity, a measure of how fast a repository is gaining stars, forks, and activity over a recent window, not by total star count. This surfaces projects that are rising quickly even if they are new. You can change the time window (today, this week, this month, and longer) and filter by language and forge.
What makes a project a "gem"?
Gems are chosen by hand. Our editors review notable projects and award gem status to ones that are genuinely useful, well-built, or interesting, regardless of how many stars they have. A gem reflects editorial judgement, not an automated threshold, and it is not an endorsement of safety or legality.
How do showcase submissions get verified?
A maintainer submits their repository, adds the GitGem.org badge to the project README, and we verify ownership by detecting that badge in the live README. Until ownership is verified, a submission stays hidden from the public feeds. The badge also gives the project a backlink, so the relationship is visible from both sides.
How does GitGem.org handle spam and low-quality repositories?
Every path that adds a repository runs the same spam scoring. Clear spam is dropped at ingest. A single ambiguous signal sends a repository to a human review queue rather than hard-blocking it, so genuine projects are not silently lost. Reviewed-and-approved repositories are permanently whitelisted.
Where does the data come from?
Repository data is pulled automatically from the public APIs of GitHub, GitLab, and Codeberg, and refreshed throughout the day. GitGem.org does not host, mirror, or distribute source code; every listing links back to the project on its original forge.
More about who runs GitGem.org on the about page.