Trending repositories

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

Period

Sort order

Tags: WebSocket library

1.SignalR / SignalR

Incredibly simple real-time web for .NET

signalr
c-sharp
asp

C#Other license9.4K total2.2K forks

+23 stars

from 9,379 · score 3.18

2.sta / websocket-sharp

A C# implementation of the WebSocket protocol client and server

C#MIT6.1K total1.7K forks

+18 stars

from 6,062 · score 2.94

3.chronoxor / NetCoreServer

Ultra fast and low latency asynchronous socket server & client C# .NET Core library with support TCP, SSL, UDP, HTTP, HTTPS, WebSocket protocols and 10K connections problem solution

low-latency
performance
async
tcp-server
tcp-client
udp-server
+11 more

C#MIT3.1K total630 forks

+18 stars

from 3,113 · score 2.94

SuperSocket is a high-performance, extensible socket server application framework for .NET. It provides a robust architecture for building custom network communication applications with support for multiple protocols including TCP, UDP, and WebSocket.

csharp
socket
socketserver
realtime-communication
tcp
udp
+3 more

C#APACHE-2.04.2K total1.2K forks

+17 stars

from 4,223 · score 2.89

5.statianzo / Fleck

C# Websocket Implementation

c-sharp
websocket
dot-net
hacktoberfest

C#MIT2.4K total592 forks

+11 stars

from 2,433 · score 2.48

6.Marfusios / websocket-client

🔧 .NET/C# websocket client library

websocket
websockets
client
dotnet-core
dotnet-standard
websocket-client
+1 more

C#MIT762 total126 forks

+8 stars

from 754 · score 2.20

7.aspnet / SignalRArchived

[Archived] Incredibly simple real-time web for ASP.NET Core. Project moved to https://github.com/aspnet/AspNetCore

aspnet-product

C#APACHE-2.02.4K total445 forks

+3 stars

from 2,356 · score 1.39

8.Code-Sharp / WampSharp

A C# implementation of WAMP (The Web Application Messaging Protocol)

c-sharp
rpc
pub-sub
wamp-protocol
websocket-subprotocol
wamp
+3 more

C#Other license389 total84 forks

+1 stars

from 388 · 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.

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