nanomsg/nanomsg

nanomsg library

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 13 minutes ago
Added to GitGenius on September 10th, 2026
Created on October 10th, 2012
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 1,029
Total Stargazers: 6,298 (+0)
Total Subscribers: 411 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.8 hours
Mean response time: 238.7 days
90th percentile: 811.6 days
Tracked items: 18

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • awaiting feedback (2)
  • release-stopper (2)
  • backburner (1)
  • feature request (1)
  • question (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

nanomsg is a messaging library that provides a socket-like interface for building distributed systems with various communication patterns.

The library addresses the complexity of implementing reliable inter-process and network communication by offering a high-level abstraction over raw sockets. Rather than forcing developers to manage TCP/UDP directly, nanomsg provides named socket types that enforce specific messaging semantics. Each socket type implements a particular communication pattern—such as request-reply, publish-subscribe, or pipeline—with built-in support for features like automatic reconnection, message queuing, and load balancing. This approach lets developers focus on application logic while the library handles the mechanical details of reliable message delivery.

Developers should choose nanomsg when building systems that need structured messaging patterns beyond simple point-to-point connections. It suits applications requiring pub-sub distribution, work queue implementations, or request-reply interactions across process or machine boundaries. The library is particularly valuable in scenarios where you want messaging semantics enforced at the transport layer rather than reimplemented in application code. Teams evaluating adoption should note that nanomsg provides a C API with bindings available for other languages, making it accessible across different technology stacks.

The project shows sustained maintenance with regular bug fixes and incremental improvements to the codebase. Development activity demonstrates responsiveness to reported issues and a commitment to stability in the core library. The maintainers prioritize backward compatibility while gradually enhancing the implementation. Updates tend to be conservative and focused on correctness rather than rapid feature expansion.