Nixpkgs is the package collection used by Nix and the repository implementing NixOS. Use it when control over package definitions and system configuration is worth the work of maintaining revisions and exceptions. Keep your existing workflow when nobody can own that work. Our run at a4b57ab installed the selected npm CI helper in 6 seconds, then its test command failed after 3 seconds because the shell could not find tsc. Nixpkgs README.
What people use nixpkgs for
Nixpkgs supports package customization and NixOS configuration, with reported uses including personal systems, declarative system management and a commercial package service. These uses involve different amounts of ownership: selecting a package, maintaining a system declaration and extending a package service are separate commitments. The official NixOS Wiki identifies the repository as a collection of Nix packages and NixOS modules. The examples below show what particular users and a vendor did with it.
| Who used it | What they did | Reported outcome |
|---|---|---|
| Reddit user ruiiiij | Ran nixos-unstable on a personal system | Generally good experience, with occasional package failures handled by pinning a version. Nixpkgs experience discussion. |
| Reddit user nixgang | Replaced Bash and then Ansible system declarations with NixOS | Said NixOS handled system declaration while presenting the resulting complexity upfront. NixOS system-declaration account. |
| Flox | Built its package service from a customized Nixpkgs repository | Reported adding semantic versioning and custom branch tracking. Flox implementation account. |
| Discourse question author | Looked for Vim and awscli2 package recipes | Accepted NixOS Search's Source link as a working navigation route. Package-source discussion. |
Flox says its Nixpkgs-flox repository tracks Nixpkgs branches directly. Its account illustrates a vendor extending the collection rather than replacing its recipes. For a smaller team, the useful question is which definitions need customization and who will maintain those changes. A personal package override and a commercial package service can both use Nixpkgs, but they call for different maintenance commitments. Flox's explanation of its repository.
What happened when we ran it
Our October 8, 2026 run at a4b57ab completed npm installation in 6 seconds, then failed its test command in 3 seconds with exit 127. The selected project was ./ci/github-script/. We measured that CI helper using a recorded sandbox configuration of 3 CPUs, 8 GB RAM and image lab-node:22. The repository scan recorded 54,845 files, approximately 137,812 source lines and 191.4 MB checked out.
| Recorded step or observation | Result |
|---|---|
| npm install in the selected helper | Succeeded in 6 seconds, with 0 dependencies recorded and 1 MB on disk |
| Build | Skipped: no build script or target |
| Test command | Failed with exit 127 in 3 seconds |
| Last error | sh: 1: tsc: not found |
| npm audit | 6 known vulnerabilities: 3 high, 3 moderate, 0 critical, 0 low |
| Repository scan | 54,845 files, approximately 137,812 source lines, 191.4 MB checked out |
| Detected signals | 17 CI workflow files, no Dockerfile, no tests directory |
| Total harness duration | 42 seconds |
The test script chained npm run typecheck && npm run testsuite. It reached tsc --build and stopped at the missing executable, so the chained testsuite was not reached. The build step had already been skipped because the selected project had no build script or target. These are the recorded outcomes; the npm audit's 6 findings belong to the selected npm scope, with 3 high and 3 moderate findings and none rated critical or low.
The November 16 hands-on safety step failed because none of compose.yaml, compose.yml, docker-compose.yaml or docker-compose.yml existed. Its rule required a Compose file, so the recorded label of unsafe describes a harness requirement. The summary nevertheless says the repository deployed with Docker Compose, with every port bound to 127.0.0.1. Those records conflict. Teardown recorded ok.
Where people get stuck: an update can remove a required package
A required package can block a rebuild when the selected Nixpkgs revision removes it, as the Brave discussion reports. Reddit user yousefmosed1 posted an error saying Brave had been removed because its maintainers lacked committers to unblock security issues. A commenter also reported that removal reached stable. That makes revision selection and package maintenance relevant to an ordinary system update, rather than only to developers changing recipes. Brave removal discussion.
Commenters suggested older package revisions and warned about retaining an outdated browser. One pointed out that a temporary pin can be forgotten after the package returns. Give an emergency browser pin an owner and a removal condition: record why it exists and what update will replace it. This is maintenance advice prompted by the reported failure, rather than an installation recipe. A successful rebuild is only one part of resolving an exception involving browser security.
| Problem in the record | Suggested route or reported result | Status in the supplied discussion |
|---|---|---|
| Brave removal blocks a rebuild | Commenters discuss package-specific pins and overlays | A workaround discussion |
| Unstable package blocks a system build | ruiiiij reports pinning the affected package | A personal workaround |
| Missing hostPlatform or legacy system setting | Error recommends setting nixpkgs.hostPlatform in hardware-configuration.nix |
A configuration error with a suggested next step |
| Package source is hard to locate | Question author accepts NixOS Search's Source link | A working navigation solution for that reader |
| GOverlay launch path fails | User reports enabling MangoHud independently works; MangoJuice lacks the desired Proton tweaks | A partial workaround |
The platform-setting error and source-search question need different responses. The first points to system configuration; the second has a navigation answer through the package's Source link. In the gaming discussion, enabling MangoHud independently worked while the GOverlay part still failed. Keeping those outcomes separate helps a reader choose the next step instead of treating every problem as the same learning-curve complaint. hostPlatform error, package-source navigation, GOverlay discussion.
Hardware compatibility needs an application-level check
Test required graphical applications and webcams on the intended machine before adopting Nixpkgs. Issue #9415 reports OpenArena installing on openSUSE 13.1 with Nix 1.9, then failing to load libGL.so.1. The IPU6 tracker records webcam results that differ by application and device. Installation, driver availability and a usable application are distinct outcomes, so a package-list entry is a poor substitute for checking the task you need. OpenGL issue #9415, IPU6 issue #225743.
| Workload | Reported outcome | Adoption decision |
|---|---|---|
| OpenArena on non-NixOS Linux | Installation succeeded, execution failed; a patched system-libGL shim was reported to work | Check the graphical application on its intended host |
| Intel IPU6 webcam | bclement-ocp reported Firefox and Webcamoid working on a Lenovo X1 Carbon Gen 10, while Cheese failed; other comments report black output and regressions | Check the camera in the application you need |
| Static Haskell executables | Tracker records successful builds and points to static-haskell-nix; general ease-of-use and documentation goals are unchecked | Allow for a specialized build workflow |
| Raspberry Pi 4 | tkerber reported a booting system, then withdrew the PR pending a consistent upstream fix | Read the historical outcome together with the withdrawal |
| Raspberry Pi 3 | Reporter described missing device trees and boot failure, then reported improvement with a newer 4.10 kernel and automatic SSH startup | Keep the result tied to its historical kernel context |
| Steam Proton 5.13 | Closed tracker records runtime-library and container-integration failures, including games still failing to launch | Distinguish tracker closure from the particular failed steps |
The static Haskell tracker also contains jgm's account of producing Pandoc's static release binaries with Docker and Alpine. The Raspberry Pi 4 discussion, Raspberry Pi 3 report and Proton 5.13 tracker describe different stages of hardware and runtime work. Read each as a report about its named configuration, including the failed steps, rather than combining them into a general compatibility verdict.
Maintenance capacity matters more than a package-count headline
Assign an owner to critical packages before adopting Nixpkgs for a team. The Brave removal report shows why package availability can depend on maintainer capacity, while a former maintainer's account describes burnout and difficulty getting changes merged. A broad catalog is useful only when the packages your work depends on remain maintainable. Start with the small set whose removal would interrupt work, then decide who follows changes and handles local exceptions. Brave discussion, contributor discussion.
In the core-team discussion, ourobo-ros says they quit package maintenance about four months earlier and describes becoming burnt out. Separately, the supplied GitHub metadata records a last push of November 17, 2026. These facts describe different things: one contributor's experience and repository activity. For background on the organizational question, the existing Nixpkgs core-team article addresses governance; this review concerns the package responsibilities an adopter takes on. Contributor account, repository metadata.
Tooling also develops around the package graph. On X, fmzakari announced a project for visualizing Nix closures and showed Git as its Nixpkgs example. That is a concrete use of the collection's dependency information. For an adopting team, however, the immediate maintenance decision is smaller: identify required packages, record local changes and decide when temporary exceptions should end. A visualization tool and a browser-maintenance plan answer different operational questions. Closure-visualization announcement.
Security starts with the source of the package definition
Assess a package definition's origin, the software's patch level and its runtime permissions separately. The Nixpkgs manual says unfree software is excluded from its continuous integration builds and cache. In the AUR comparison thread, GlassCommission4916 describes Nixpkgs pull requests as requiring a trusted maintainer's check. These are different kinds of evidence: a documented build policy and an attributed explanation of review practice. Nixpkgs manual, Nixpkgs vs AUR discussion.
The Zen Browser thread illustrates why origin matters. MarceColl offered an external flake using the binary release while source packaging was being worked out, and chaezwav reported that it built and worked. That outcome belongs to the external flake described in the discussion. Keep its source and update process visible in your configuration notes, just as you would for a local patch or temporary revision pin. Zen Browser packaging issue.
Nixpkgs vs AUR, Homebrew, Flatpak and flakes
Choose the workflow by the job: Nixpkgs supplies package definitions and NixOS modules, while Flatpak focuses on Linux desktop applications and Homebrew directs users to formulae and casks. Flakes can carry Nixpkgs itself; the supplied module tutorial includes it as an input. These relationships make a single winner less useful than a decision about package sources, system configuration and the software you already maintain. Module tutorial, Homebrew README, Flatpak README.
| Alternative or adjacent tool | Evidence behind the comparison | When to choose that route |
|---|---|---|
| AUR | Reddit commenters contrast user uploads with trusted review of Nixpkgs changes | Keep an existing Arch workflow when it meets your needs and you assess individual recipes |
| Homebrew | Its README points to formulae, casks, dependencies and version metadata | Keep it when its catalog covers your tools and Nix configuration adds no needed capability |
| Flatpak | Its README describes building, distributing and running sandboxed Linux desktop applications | Consider it for a Linux desktop application |
| Upstream package flakes | The Helix tutorial describes obtaining an upstream version and compiling from source | Consider the route when you need that version and can maintain its source selection |
| Bash and Ansible | nixgang reports replacing both with NixOS system declarations | Keep existing scripts when taking on NixOS configuration is outside your intended work |
The AUR discussion, Helix tutorial and system-declaration account explain the community comparisons in the table. Homebrew's catalog provides an entry point for checking an existing tool requirement; Flatpak's stated desktop focus provides another. Selecting one desktop application's distribution route still leaves the separate question of how you want to configure an operating system. Use the required software and configuration task to make that choice.
What the other reviews get wrong
Nixpkgs includes expressions for unfree software, so calling it a recipe book of all open source needs a licensing qualification. The repository's MIT license covers its files, including expressions, scripts and modules; built packages retain their respective licenses. Flox's description is useful for explaining recipes, but it should not become a blanket licensing statement about everything those recipes build. Flox overview, manual licensing discussion, repository license explanation.
The categorical claim quoted in the departure discussion that Nix dependencies cannot be split into separate layers is too broad. A commenter identifies buildLayeredImage and streamLayeredImage as helpers that produce separate dependency layers. This corrects the specific tooling claim. It also gives readers a more useful starting point than repeating a broad dismissal of Nix-based image construction. Docker-layering discussion.
Stable-channel descriptions should include conservative critical-bug fixes as well as security fixes, matching the official wiki. Package counts need their snapshot context too: the nix-community fork says over 40,000, while the supplied unstable search snapshot lists 151,973 packages at revision d5cc6833. The older lower bound and the newer snapshot are different descriptions, rather than interchangeable measures of current package availability. Stable-channel explanation, fork README, unstable search snapshot.
FAQ
Nixpkgs supplies packages for Nix and implements NixOS; nixpkgs-review is a separate tool that builds packages changed by pull requests. That distinction matters when looking for a review, package source or contribution workflow. The repository README separates the manuals for package-manager commands, package expressions and operating-system configuration. Choose the manual for the layer you intend to change. Nixpkgs README, nixpkgs-review README.
What is Nixpkgs, and how does it differ from Nix and NixOS?
Nix is the package manager, Nixpkgs is its package collection, and NixOS is the Linux distribution implemented in the repository. The README links a Nix manual for expressions and command-line tools, a Nixpkgs manual for contribution and language-specific expressions, and a NixOS manual for installation and system configuration. Start with the part you need rather than treating all three names as interchangeable. Project README.
What do actual users like and dislike about Nixpkgs?
The sampled users describe useful system declaration alongside package failures and documentation friction. ruiiiij reports a generally good nixos-unstable experience with occasional pins; nixgang values declaring the system while accepting upfront complexity; mister_drgn criticizes the documentation. These accounts help identify the maintenance decisions involved in adoption. Read them against your own requirements: a personal system and a team's required browser can tolerate different kinds of interruption. User-experience discussion.
How do I search Nixpkgs and find a package's source on GitHub?
Follow a package's Source link from NixOS Search to its recipe on GitHub. The Discourse question author accepted that method after trying to locate Vim and awscli2 in the repository tree. The thread also gives a branch-specific search command, nix search github:NixOS/nixpkgs/nixos-unstable foo. Keep the selected branch or revision with your notes so the recipe location and package result have an identifiable context. Package-source search discussion.
Which Nixpkgs manual and contribution guide should I read first?
Read the Nixpkgs manual for contribution and programming-language-specific expressions, then the repository's contribution guide before submitting a change. Use the Nix manual when the question concerns expressions or command-line tools instead. The NixCon2024 contributor talk recommends beginning with a small bug or version bump. That gives a first contribution a concrete scope rather than starting with a large service or a broad configuration rewrite. README manual links, NixCon2024 contributor talk.
What is the difference between nixpkgs-unstable and nixos-unstable?
The official wiki describes basic package build tests for nixpkgs-unstable and system-oriented VM integration tests for nixos-unstable. The distinction concerns what the channel checks before advancement. Stable branches receive conservative fixes for critical bugs and security vulnerabilities. When selecting a channel or reporting a problem, include the actual branch and revision rather than using unstable as though it identifies one configuration. Official channel explanation.
How do I track when a merged Nixpkgs PR reaches my channel?
A merged pull request and a channel update are separate events: the README says expressions reach channels after successful build and test criteria are met. Record the revision containing the change and the revision your configuration selects when checking whether you have it. This keeps the question tied to the package definitions in use, rather than assuming that a merge immediately changes an existing environment. README distribution explanation.
Where do I search NixOS options and report Nixpkgs issues?
The official wiki points to package and option search, and the README welcomes GitHub issues and pull requests in NixOS/nixpkgs. Package search locates software; option search concerns configuration. For a useful problem report, include the selected revision and the concrete error you encountered. The hostPlatform discussion illustrates how a specific configuration error gives a more actionable starting point than a general report that rebuilding failed. Official wiki, repository contribution routes, hostPlatform discussion.
How does Nixpkgs security compare with the AUR?
GlassCommission4916 describes Nixpkgs changes as requiring a trusted maintainer's check, contrasting that process with AUR uploads. Other commenters identify NUR and arbitrary GitHub flakes as closer user-repository comparisons. The practical distinction is the origin and review process of the definition you select. Keep that question separate from the packaged application's patch level and runtime permissions when deciding whether it meets your requirements. Nixpkgs vs AUR discussion.
What we have not tested yet
Our measured execution covers the Node CI helper at a4b57ab and a blocked Compose attempt, rather than Nix installation, a Nix package build or a working NixOS system. Package evaluation, cold search, cache downloads, closure size and application startup remain outside those measurements. The image label supplies no actual runtime or operating-system version. Raw logs are needed to diagnose the missing compiler, identify affected audit dependency paths and establish audit coverage; the scanner signals are not an exhaustive inventory of repository validation.
The November 16 deployment summary conflicts with its failed safety step. The supplied attempt contains no successful application-task results, hands-on question-answer session or screenshot records to resolve that conflict. Setup, documentation, community and maturity remain numerically unassessed: this sample supplies neither a supported Nix setup result nor measurements of documentation usability, support responsiveness or operational reliability. No corrected command or new code example was executed for this revision.
The community and issue outcomes belong to their authors and recorded configurations. We have not reproduced the webcam, OpenGL, browser, Haskell, GOverlay, Steam or Raspberry Pi workflows, checked the current resolution of the historical trackers, or confirmed Brave's current availability. The reported library shim and kernel changes are historical accounts, not current installation instructions. The supplied evidence also leaves comparative security, runtime sandbox isolation, alternative-workflow performance, company adoption and Flox fork-maintenance costs unmeasured.
Autocomplete supplies names but no substantive workflows for Nixpkgs Multiverse, a Codex integration, VS Code extensions or VSCodium setup. Service-specific PR-tracker instructions are also absent. Search volumes, ranks and demand are unknown. The next useful evaluation is one required package on the intended machine, followed by an update of that same configuration, with the revision and application outcome recorded. Rendered layout, resolved links, accessibility and site recommendation modules also require a separate check.


