nixos/nix

Nix, the purely functional package manager

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 3rd, 2026
Created on February 8th, 2012
Open Issues & Pull Requests: 2,948 (+0)
GitHub issues: Enabled
Number of forks: 1,995
Total Stargazers: 17,655 (+0)
Total Subscribers: 137 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 20.1 hours
Mean response time: 201.8 days
90th percentile: 882.4 days
Tracked items: 2,932

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 61% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "installer" is answered fastest, typically in about 5 hours, while "documentation" waits about 5 days. 67% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 2% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,220
New in 7 days: 8
Closed in 7 days: 9
Avg open age: 1,020 days
Stale 30+ days: 1,016
Stale 90+ days: 809

Recent activity

Opened in 7 days: 7
Closed in 7 days: 4
Comments in 7 days: 1
Events in 7 days: 4

Top labels

  • bug (1,365)
  • stale (643)
  • feature (514)
  • installer (294)
  • UX (156)
  • documentation (144)
  • language (108)
  • flakes (98)

Detailed Description

Nix is a purely functional package manager for Linux and other Unix systems that makes package management reliable and reproducible.

Nix solves the problem of dependency hell and irreproducible builds by treating packages as pure functions with explicit inputs and outputs. Every package build is isolated and deterministic, meaning the same inputs always produce identical outputs regardless of the system state. This functional approach eliminates hidden dependencies and system-wide state that cause builds to fail unpredictably across different machines or over time.

Nix suits developers and operators who prioritize reproducibility and reliability over convenience. It works well for projects requiring consistent build environments across teams, for managing complex dependency graphs, and for systems where you need to pin exact versions and guarantee that builds remain valid years later. The tool integrates with a broader ecosystem including Nixpkgs, a declarative package repository, and NixOS, a Linux distribution configured entirely through Nix declarations. Adoption requires learning Nix's functional language and rethinking how you specify dependencies, so it is most valuable when reproducibility is a core requirement rather than a nice-to-have.

The project maintains active engagement with both its core team and external contributors. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on bugs, features, and installer improvements, with open issues reflecting a healthy mix of internal priorities and external user needs.