macOS
Homebrewverified · 100%
brew install nsqlocal Homebrew formula metadata
brew / rank 6700
Install nsq with Homebrew, apk, Nix
Realtime distributed messaging platform. Version 1.3.0 via Homebrew; verified 2026-06-06. Also installable with nix: nix profile install nixpkgs#nsq.
install
Additional install commands
Linux
Alpine Linux apkverified · 92%
sudo apk add nsqAlpine Linux edge package indexes · nsq · source: dl-cdn.alpinelinux.org
Nixverified · 92%
nix profile install nixpkgs#nsqnixpkgs package indexes · pkgs/by-name/ns/nsq/package.nix · source: api.github.com
overview
Package summary
Realtime distributed messaging platform
Project links
Commands and aliases
- nsq_stat
- nsq_tail
- nsq_to_file
- nsq_to_http
- nsq_to_nsq
- nsqadmin
- nsqd
- nsqlookupd
- to_nsq
history
Project history and usage
NSQ is a Go-based realtime distributed messaging platform from Bitly's engineering ecosystem. It was built for decentralized message processing, using `nsqd` producers/queues, `nsqlookupd` discovery, and `nsqadmin` operations tooling instead of a single centralized broker.
Project history
Bitly announced NSQ publicly in October 2012 as a realtime message processing system designed for Bitly's scale and billions of messages per day. The NSQ community page credits Matt Reiferson and Jehiah Czebotar as the designers and developers, with support from Bitly, maintainers, and contributors.
Adoption history
The December 2012 Bitly follow-up said NSQ had been released on October 9, 2012, had client libraries in seven languages, and had quickly become one of the most-watched Go projects on GitHub. NSQ's later homepage kept the same positioning: distributed topologies without single points of failure, horizontal scaling without centralized brokers, and both pub-sub and load-balanced delivery.
On July 1, 2026, Homebrew listed NSQ 1.3.0 with 273 installs in its 365-day analytics window. That is modest Homebrew usage, but the package remains useful for developers who need local NSQ daemons and CLI tools while testing older or deliberately simple queueing architectures.
How it is used
Package users install NSQ to get the daemons and operational tools: `nsqd` receives, queues, and delivers messages; `nsqlookupd` lets consumers discover producers; `nsqadmin` provides a web UI; helper commands such as `nsq_tail`, `nsq_to_file`, `nsq_to_http`, and `to_nsq` make it easy to inspect or bridge streams.
The important operational tradeoff is explicit in the docs: NSQ is primarily in-memory, can spill past a memory queue threshold, provides at-least-once delivery, does not guarantee ordering, and expects clients to be idempotent or de-duplicate work.
Why package nerds care
NSQ is a classic small distributed-systems package: easy to run, easy to reason about, and intentionally less feature-heavy than Kafka-class systems. It is most attractive when a team wants simple producer-local queueing, HTTP/TCP protocols, and discovery without operating a broker cluster.
Timeline
- October 9, 2012: NSQ was released publicly by Bitly.
- December 2012: Bitly reported client libraries in seven languages and early strong GitHub attention.
- July 1, 2026: Homebrew listed NSQ 1.3.0.
Related projects
- go-nsq is the official Go client package for NSQ.
Sources
security posture
Risk level: orange
broad file, network, media, or database tool signal. formula declares a Homebrew service.
Risk classifier
orange risk · medium confidence · infrastructure
Why
- broad file, network, media, or database tool signal
- formula declares a Homebrew service
Signals
- metadata:service
- text:http,sql
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
nsq_stat | executable | indexed executable | Discovered from the local executable index. |
nsq_tail | executable | indexed executable | Discovered from the local executable index. |
nsq_to_file | executable | indexed executable | Discovered from the local executable index. |
nsq_to_http | executable | indexed executable | Discovered from the local executable index. |
nsq_to_nsq | executable | indexed executable | Discovered from the local executable index. |
nsqadmin | executable | indexed executable | Discovered from the local executable index. |
nsqd | executable | indexed executable | Discovered from the local executable index. |
nsqlookupd | executable | indexed executable | Discovered from the local executable index. |
to_nsq | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version1.3.0
manager updated2026-06-06
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:nsq |
|---|---|
| Version | 1.3.0 |
| Package manager | Homebrew |
| Homepage | https://nsq.io/ |
| Repository | https://github.com/nsqio/nsq |
| Last updated | 2026-06-06T11:29:13Z |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
Nix95%
nsq
nix profile install nixpkgs#nsq- normalized package name match
- Matched by: Nsq
apk95%
nsq 1.3.0-r10
A realtime distributed messaging platform
sudo apk add nsq- License: MIT
- Architecture: x86_64
- Source Package: nsq
- 1 dependencies
- 1 provides
- normalized package name match
- Matched by: Nsq
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated package history
- external package-manager database matches
- pkg.so package database
- pkgdb category and tag curation