A community-driven meta repository for Nix packages, providing decentralized access to user-contributed packages and modules.
NUR (Nix User Repository) is a community-driven meta repository for Nix packages that aggregates user-contributed package descriptions and expressions. It provides a decentralized alternative to Nixpkgs, allowing users to share and install packages without central review. The repository automatically checks and evaluates updates from contributed repositories.
Nix and NixOS users who want access to community-contributed packages, experimental builds, or niche software not available in the main Nixpkgs repository.
Developers choose NUR for its decentralized approach, faster package updates, and support for experimental or user-specific packages that may not meet Nixpkgs inclusion criteria. It complements Nixpkgs by enabling community-driven sharing without central review bottlenecks.
Nix User Repository: User contributed nix packages [maintainer=@Pandapip1]
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Aggregates user-contributed packages from independent repositories, enabling faster sharing of experimental and niche software without Nixpkgs review bottlenecks, as stated in the philosophy.
Provides not only packages but also NixOS modules, Home Manager modules, overlays, and library functions, offering versatile integration for various Nix setups, as highlighted in the key features.
Regularly evaluates repositories and performs checks before propagating updates, adding a layer of quality control despite the lack of central review, as mentioned in the automatic updates section.
Supports modern Nix flakes with overlays and modules, along with legacy methods like packageOverrides, ensuring compatibility across different Nix workflows, as shown in the installation examples.
Packages are not reviewed for malicious content, and the README explicitly warns users to check expressions before installation, increasing security risks compared to Nixpkgs.
All packages are built from source without centralized binary caches, leading to longer installation times and potential build failures, unlike Nixpkgs which leverages caching.
Community-driven contributions can result in broken or outdated packages, as indicated by the contribution guidelines advising to set meta.broken for non-working packages.
Overriding repositories for testing requires manual configuration with repoOverrides, which adds complexity and is described as experimental for flake support, limiting ease of use.