1
0
Fork 1
mirror of https://github.com/NixOS/nixpkgs.git synced 2025-06-08 02:38:11 +09:00
No description
Find a file
2025-06-07 08:07:28 +02:00
.github workflows/check-cherry-picks: minimize more than one old review 2025-06-02 21:08:25 +00:00
ci ci/nixpkgs-vet: fix random errors 2025-06-02 20:07:34 +00:00
doc doc: fix pypy39 removal 2025-06-01 13:46:36 +00:00
lib lib/tests: avoid full rebuild when only maintainers change 2025-06-02 07:45:16 +00:00
maintainers maintainers: donteatoreo add matrix 2025-05-29 22:03:18 +05:30
nixos nixos/gitlab: fix ardeterministic secret 2025-06-03 14:52:22 +02:00
pkgs [24.11] curlMinimal: backport patch for CVE-2025-5399 (#413957) 2025-06-07 08:07:28 +02:00
.editorconfig treewide: fix editorconfig ci check 2025-05-14 17:46:43 +02:00
.git-blame-ignore-revs git-blame-ignore-revs: Add previous commit 2025-04-01 20:11:51 +02:00
.gitattributes .gitattributes: Mark ci/OWNERS as CODEOWNERS 2024-10-10 01:40:43 +02:00
.gitignore gitignore: ignore worktrees 2025-03-31 05:16:24 +00:00
.mailmap mailmap: add jopejoe1 2025-01-20 10:23:37 +00:00
.version
CONTRIBUTING.md CONTRIBUTING: Improve and update formatting docs 2025-04-01 20:10:57 +02:00
COPYING
default.nix treewide: format all inactive Nix files 2024-12-10 20:29:24 +01:00
flake.nix flake: fix nix flake check --all-systems --no-build again 2025-04-04 07:36:37 -07:00
README.md README: Update to 24.11 2024-11-30 15:06:14 +00:00
shell.nix shell: Introduce treefmt 2025-04-01 20:10:56 +02:00

NixOS logo

Contributors badge Open Collective supporters

Nixpkgs is a collection of over 100,000 software packages that can be installed with the Nix package manager. It also implements NixOS, a purely-functional Linux distribution.

Manuals

  • NixOS Manual - how to install, configure, and maintain a purely-functional Linux distribution
  • Nixpkgs Manual - contributing to Nixpkgs and using programming-language-specific Nix expressions
  • Nix Package Manager Manual - how to write Nix expressions (programs), and how to use Nix command line tools

Community

Other Project Repositories

The sources of all official Nix-related projects are in the NixOS organization on GitHub. Here are some of the main ones:

  • Nix - the purely functional package manager
  • NixOps - the tool to remotely deploy NixOS machines
  • nixos-hardware - NixOS profiles to optimize settings for different hardware
  • Nix RFCs - the formal process for making substantial changes to the community
  • NixOS homepage - the NixOS.org website
  • hydra - our continuous integration system
  • NixOS Artwork - NixOS artwork

Continuous Integration and Distribution

Nixpkgs and NixOS are built and tested by our continuous integration system, Hydra.

Artifacts successfully built with Hydra are published to cache at https://cache.nixos.org/. When successful build and test criteria are met, the Nixpkgs expressions are distributed via Nix channels.

Contributing

Nixpkgs is among the most active projects on GitHub. While thousands of open issues and pull requests might seem a lot at first, it helps consider it in the context of the scope of the project. Nixpkgs describes how to build tens of thousands of pieces of software and implements a Linux distribution. The GitHub Insights page gives a sense of the project activity.

Community contributions are always welcome through GitHub Issues and Pull Requests.

For more information about contributing to the project, please visit the contributing page.

Donations

The infrastructure for NixOS and related projects is maintained by a nonprofit organization, the NixOS Foundation. To ensure the continuity and expansion of the NixOS infrastructure, we are looking for donations to our organization.

You can donate to the NixOS foundation through SEPA bank transfers or by using Open Collective:

License

Nixpkgs is licensed under the MIT License.

Note: MIT license does not apply to the packages built by Nixpkgs, merely to the files in this repository (the Nix expressions, build scripts, NixOS modules, etc.). It also might not apply to patches included in Nixpkgs, which may be derivative works of the packages to which they apply. The aforementioned artifacts are all covered by the licenses of the respective packages.