zeromq/netmq

A 100% native C# implementation of ZeroMQ for .NET

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 21st, 2026
Created on November 3rd, 2012
Open Issues & Pull Requests: 135 (+0)
GitHub issues: Enabled
Number of forks: 763
Total Stargazers: 3,180 (+0)
Total Subscribers: 202 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.6 days
Mean response time: 202.7 days
90th percentile: 503.2 days
Tracked items: 48

How this project is maintained

96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 77% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 28
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 954 days
Stale 30+ days: 27
Stale 90+ days: 26

Recent activity

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

Top labels

  • stale (4)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

NetMQ is a 100% native C# port of the lightweight messaging library ZeroMQ for .NET.

NetMQ solves the problem of adding sophisticated messaging capabilities to .NET applications without requiring external dependencies or native libraries. It extends standard socket interfaces with asynchronous message queues, multiple messaging patterns, message filtering through subscriptions, and seamless access to multiple transport protocols. By porting ZeroMQ directly to C#, the tool eliminates the need to interoperate with native ZeroMQ binaries while preserving the messaging patterns and abstractions that make ZeroMQ valuable.

Developers should choose NetMQ when building .NET applications that require reliable inter-process or network communication with support for patterns like request-reply, publish-subscribe, and push-pull. It suits projects where you want ZeroMQ's messaging model without managing native dependencies. The project maintains two versions: a stable version and a newer version with obsolete code removed, allowing teams to choose based on their migration readiness.

The project maintains active engagement through a mailing list for community discussion and accepts contributions following a formal specification process. Documentation is available through a dedicated site and supplemented by community blog posts covering socket types, polling, and messaging patterns. The maintainer provides consulting services, indicating sustained involvement with the project's direction and real-world usage scenarios.