lsalzman/enet

ENet reliable UDP networking library

View on GitHub ↗Jump to charts ↓

lsalzman/enet has 3k+ stars and 700+ forks on GitHub, is written in C, and was last pushed on Jun 23, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on May 5th, 2012
Open Issues & Pull Requests: 98 (+0)
GitHub issues: Enabled
Number of forks: 738
Total Stargazers: 3,291 (+0)
Total Subscribers: 155 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.3 days
Mean response time: 70.5 days
90th percentile: 163.5 days
Tracked items: 12

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 624 days
Stale 30+ days: 9
Stale 90+ days: 9

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

ENet is a reliable UDP networking library written in C that provides a lightweight alternative to TCP for games and real-time applications.

ENet solves the problem of needing ordered, reliable packet delivery over UDP without the overhead and latency characteristics of TCP. It works by implementing a custom protocol on top of UDP that guarantees packet ordering and delivery while maintaining the lower latency and reduced overhead of datagram-based communication. The library handles packet fragmentation, acknowledgment, and resend logic internally, allowing developers to send variable-sized messages without managing these concerns themselves.

ENet suits projects where network responsiveness matters more than the guarantees of TCP, particularly multiplayer games and other real-time networked applications. It is designed to be minimal and portable, making it appropriate for embedded networking needs where a full TCP stack would be overkill. Developers choosing ENet should expect to work with a C library that requires manual memory management and direct socket handling, trading convenience for control and efficiency.

The project shows sparse but consistent maintenance activity. Development involves occasional bug fixes and minor improvements to the codebase rather than frequent feature additions. The maintainer responds to issues and pull requests but at a measured pace, suggesting the library is treated as a stable, mature tool rather than one undergoing active expansion. The project remains functional and usable despite the infrequent update cadence.