Trending repositories

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

Period

Sort order

Tag

Filters (1)

Apply

Filters

Primary language

License

Total stars

Last push

Created

Archived

Clear all filters

9 repositories by Attention Score · Aug 6, 2026 – Nov 3, 2026 (UTC)

Language: Erlang
Tag: Backend and APIs
Clear all

1.ninenines / cowboy

Small, fast, modern HTTP server for Erlang/OTP.

erlang
http
http2
http-server
websocket
websockets
+13 more

Erlang ISC7.5K total1.2K forks

+15 stars

from 7,506 · score 2.77

2.ninenines / ranch

Socket acceptor pool for TCP protocols.

Erlang ISC1.2K total335 forks

+7 stars

from 1,239 · score 2.08

3.benoitc / hackney

simple HTTP client in Erlang

http
client
erlang

Erlang Other license1.4K total457 forks

+6 stars

from 1,413 · score 1.95

4.ninenines / gun

HTTP/1.1, HTTP/2, Websocket client (and more) for Erlang/OTP.

http
https
http-client
http2
http2-client
websocket
+11 more

Erlang ISC949 total243 forks

+6 stars

from 943 · score 1.95

5.zotonic / zotonic

Zotonic - The Erlang Web Framework & CMS

erlang
cms
web
framework
zotonic

Erlang APACHE-2.0851 total208 forks

+5 stars

from 846 · score 1.79

6.mochi / mochiweb

MochiWeb is an Erlang library for building lightweight HTTP servers.

Erlang Other license1.9K total460 forks

+3 stars

from 1,886 · score 1.39

7.ChicagoBoss / ChicagoBoss

Erlang web MVC, now featuring Comet

framework
web-framework
erlang

Erlang MIT1.8K total283 forks

+1 stars

from 1,847 · score 0.69

8.synrc / n2o

⭕ N2O: Distributed WebSocket Application Server ISO 20922

websockets
mqtt
tcp
udp
bert

Erlang Other license1.3K total167 forks

+1 stars

from 1,340 · score 0.69

9.gossiperl / gossiperl

Gossip middleware in Erlang

Erlang MIT48 total6 forks

+1 stars

from 47 · score 0.69

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.

Repositories enter the index from the starting dataset of the index, or by gaining stars faster than the published admission threshold, whatever their size. A repository stays in the index after it enters. Thus an archived repository can still rank.

Browse the Repository Index