leahneukirchen/nq

Unix command line queue utility

View on GitHub ↗Jump to charts ↓

leahneukirchen/nq has 3k+ stars and 60+ forks on GitHub, is written in C, and was last pushed on Oct 26, 2025. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 46 minutes ago
Type:CLI ToolCategory(s):CLI UtilitiesDeveloper Tools
Added to GitGenius on September 22nd, 2026
Created on July 31st, 2015
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 69
Total Stargazers: 3,136 (+0)
Total Subscribers: 46 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.2 hours
Mean response time: 0.2 hours
90th percentile: 0.2 hours
Tracked items: 1

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

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

nq is a Unix command line queue utility that manages job execution through a simple file-based queueing system.

The tool solves the problem of running jobs sequentially or with controlled concurrency without requiring a heavy daemon or complex setup. It works by storing jobs in a queue directory and executing them in order, with each job represented as a file. The approach is minimal and portable, relying on standard Unix primitives like file locking to coordinate between multiple queue instances.

The tool suits developers and system administrators who need lightweight job scheduling without the overhead of cron, at, or a full job queue system. It works well for simple sequential task execution, build pipelines, or any scenario where you need to serialize work across multiple invocations. The file-based design means queues persist across system restarts and can be inspected directly on the filesystem. It is particularly useful in shell scripts and automation where you want straightforward job ordering without external dependencies.

Development activity shows consistent maintenance with regular bug fixes and incremental improvements to the core queueing logic. The project receives updates that address edge cases and enhance reliability of the file-locking mechanism. Changes are focused and deliberate, targeting specific issues rather than broad feature expansion. The codebase remains stable and well-tested, with attention paid to ensuring correct behavior under concurrent access patterns.