Trending repositories

Ranked by Attention Score: stars gained over the last 180 complete days

Period

Sort order

Tags: All Tags

1.Wei-Shaw / sub2api

TranslatedSub2API is a one-stop open-source relay service that lets Claude, Openai, Gemini, and Grok subscriptions be accessed in one unified way. It supports car-pool sharing to split costs more efficiently, and native tools can be used seamlessly.

2api
antigravity2api
claude
claude-code
codex
crs
+3 more

Go LGPL-3.045K total9.8K forks

+26,922 stars

from 18,520 · score 10.20

2.ethereum / go-ethereum

Go implementation of the Ethereum protocol

go
blockchain
ethereum
p2p
geth

Go LGPL-3.051K total22K forks

+785 stars

from 50,674 · score 6.67

3.peterq / pan-light

TranslatedBaidu Netdisk (Baidu Pan) client with no speed limit, golang + qt5, cross-platform graphical interface

golang
qt5
qml
baiduyun

Go LGPL-3.012K total2.4K forks

+78 stars

from 12,047 · score 4.37

4.therecipe / qt

Qt binding for Go (Golang) with support for Windows / macOS / Linux / FreeBSD / Android / iOS / Sailfish OS / Raspberry Pi / AsteroidOS / Ubuntu Touch / JavaScript / WebAssembly

go
gui-framework
qt
cross-platform-gui
windows
macos
+12 more

Go LGPL-3.011K total744 forks

+70 stars

from 10,735 · score 4.26

5.NicoNex / echotron

An elegant and concurrent library for the Telegram bot API in Go.

go
telegram-bot
telegram-bot-api
telegram
telegram-api
bot
+4 more

Go LGPL-3.0448 total26 forks

+20 stars

from 428 · score 3.04

6.ihexxa / quickshare

Quick and simple file sharing between different devices, built with Go, React and Typescript.

go
golang
javascript
reactjs
webpack
yarn
+6 more

Go LGPL-3.0639 total41 forks

+11 stars

from 628 · score 2.48

7.spyre-project / spyre

simple YARA-based IOC scanner

yara
ioc
security
incident-response
hacktoberfest
windows
+7 more

Go LGPL-3.0185 total30 forks

+8 stars

from 177 · score 2.20

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before the first daily record that AwesomeRepos made for the repository. A longer window needs more of these daily records first. A repository younger than the window does not rank in it.

The filters select from the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Tag holds the repositories that have it. See Tags.

A new repository enters the index when it gains stars faster than the published admission threshold, whatever its size. A repository stays in the index after it enters. Thus an archived repository can still rank.

Browse the Repository Index