nixpkgs VS git-lfs

Compare nixpkgs vs git-lfs and see what are their differences.


Git extension for versioning large files (by git-lfs)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
nixpkgs git-lfs
969 159
15,511 12,405
4.4% 1.2%
10.0 9.1
6 days ago 13 days ago
Nix Go
MIT License GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of nixpkgs. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-02.
  • The xz attack shell script
    5 projects | | 2 Apr 2024
    I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs
  • Debian Git Monorepo
    4 projects | | 2 Apr 2024
    NixOS uses a monorepo and I think everyone's love it.

    I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.

    Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.

  • From xz to ibus: more questionable tarballs
    5 projects | | 1 Apr 2024
    In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].



  • GitHub Disabled the Xz Repo
    5 projects | | 29 Mar 2024
    does depend on lzma.

    A quick glance at

    does not show a direct dependency.

    5 projects | | 29 Mar 2024
    True, but irrelevant -- _some packages_, _somewhere_, do depend on xz, which, if built, requires pulling the source from GitHub (see the default.nix:

    It's not the vulnerability that's a problem right now (NixOS was protected by a couple of factors) but rather GitHub's hamfisted response.

    That is the problem.

  • Combining Nix with Terraform for better DevOps
    4 projects | | 19 Mar 2024
    We’ve noticed that some users have been asking about how to use older versions of Terraform in their Nix setups [1, 2]. This is an example of the diverse needs of people and the importance of maintaining backward compatibility. We hope that nixpkgs-terraform will be a useful tool for these users.
  • Nix is a better Docker image builder than Docker's image builder
    21 projects | | 15 Mar 2024
    I think whateveracct was referring to is this link:

    What that file is doing, is building a package, and it essentially is a combination of what Makefile and what RPM spec file does.

    I don't know if you're familiar with those tools, but if you aren't it takes some time to know them enough to understand what is happening. So why would be different here?

    21 projects | | 15 Mar 2024
    That's doesn't happen in a single thread, but e.g. asynchronous multithreaded code can spit values in arbitrary order, and depending on what you do you can end up with a different result (floating point is just an example). Generally, you can't guarantee reproducibility because there's too much hardware state that can't be isolated even in a VM. Sure, 99% software doesn't depend on it or do cursed stuff like microarchitecture probing during building, and you won't care until you try to package some automated tests for a game physics engine or something like that. What can happen, inevitably happens.

    We don't need to be looking for such contrived examples actually, nixpkgs track the packages that aren't reproducible for much more trivial reasons:

    21 projects | | 15 Mar 2024
    - trim boto3/botocore, to remove all stuff I did not use, that sucker on it's own is over 100MB

    The thing is what you need to understand is that the packages are primarily targeting the NixOS operating system, where in normal situation you have plenty of disk space, and you rather want all features to be available (because why not?). So you end up with bunch of dependencies, that you don't need. Alpine image for example was designed to be for docker, so the goal with all packages is to disable extra bells and whistles.

    This is why your result is bigger.

    To build a small image you will need to use override and disable all that unnecessary shit. Look at zulu for example:

    you add alsa, fontconfig (probably comes with entire X11), freetype, xorg (oh, nvm fontconfig, it's added explicitly), cups, gtk, cairo and ffmpeg)

    Notice how your friend carefully extracts and places only needed files in the container, while you just bundle the entire zulu package with all of its dependencies in your project.

  • Use Ansible to create and start LXD virtual machines
    2 projects | | 12 Mar 2024
    #!/usr/bin/env nix-shell #! nix-shell -i bash #! nix-shell -p sops #! nix-shell -I source "$@"


Posts with mentions or reviews of git-lfs. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-04.
  • Twenty Years Is Nothing
    4 projects | | 4 Mar 2024
  • Aho – a Git implementation in Awk
    8 projects | | 10 Feb 2024
    It doesn't, since Git's data model has to be changed to content-defined chunks to solve the issue.

    You should look at git-lfs[1] instead.


  • Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
    5 projects | | 22 Jan 2024
    Congrats on the HN launch. How does this improve or expand or blow git-lfs[1] out of the water because if I needed large blob file support it's what I would use instead. It offers pointers to the big files to the hosted git instead of pushing around the binaries itself -- though I am speculating since I've not used it myself just read about it online.


  • Ask HN: Can we do better than Git for version control?
    17 projects | | 10 Dec 2023
    fine with layers: e.g., large binary files via git-lfs ( and merge conflicts in non-textual files by custom merge resolvers like Unity’s (

    Perhaps in the future, almost everyone will keep using Git at the core, but have so many layers to make it more intuitive and provide better merges, that what they’re using barely resembles Git at all. This flexibility and the fact that nearly everything is designed for Git and integrates with Git, are why I doubt it’s ever going away.

    Some alternatives for thought:

    - pijul (, a completely different VCS which allegedly has better merges/rebases. In beta, but I rarely hear about it nowadays and have heard more bad than good. I don’t think we can implement this alternate rebases in Git, but maybe we don’t need to; even after reading the website, I don’t understand why pijul’s merges are better, and in particular I can’t think of a concrete example nor does pijul provide one.

    - Unison ( This isn’t a VCS, but a language with a radical approach to code representation: instead of code being text stored in files, code is ASTs referenced by hash and stored in essentially a database. Among other advantages, the main one is that you can rename symbols and they will automatically propagate to dependencies, because the symbols are referenced by their hash instead of their name. I believe this automatic renaming will be common in the future, whether it’s implemented by a layer on top of Git or alternate code representation like Unison (to be clear, Unison’s codebases are designed to work with Git, and the Unison project itself is stored in Git repos).

    - SVN, the other widespread VCS. Google or ask ChatGPT “Git vs SVN” and you’ll get answers like this (, Basically, SVN is easier to understand and handles large files better, Git is decentralized and more popular. But what about the differences which can’t be resolved by layers, like lazygit for intuition and git-lfs for large files? It seems to me like even companies with centralized private repositories use Git, meaning Git will probably win in the long term, but I don’t work at those companies so I don’t really know.

    - Mercurial and Fossil, the other widespread VCSs. It seems these are more similar to Git and the main differences are in the low-level implementation (, It actually seems like most people prefer Mercurial and Fossil over Git and would use them if they had the same popularity, or at least if they had Git’s popularity and Git had Mercury or Fossil’s. But again, these VCSs are so similar that with layers, you can probably create a Git experience which has their advantages and almost copies their UI.

  • We Put Half a Million Files in One Git Repository, Here's What We Learned (2022)
    4 projects | | 28 Aug 2023
  • Show HN: Gogit – Just enough Git (in Go) to push itself to GitHub
    8 projects | | 29 Jul 2023
    I don’t know what that is, but their docs very prominently and strongly say this:

    > However, we do not maintain a stable Go language API or ABI, as Git LFS is intended to be used solely as a compiled binary utility. Please do not import the git-lfs module into other Go code and do not rely on it as a source code dependency.

    8 projects | | 29 Jul 2023
    > I don’t know what that is

    its a standard output from `go doc`, rendered as HTML. if you dont recognize that, then you aren't really in a position to be commenting on the topic. nothing is stopping anyone from pinning to a tag:

    or even a commit and relying of a specific version of the software. yes upgrades might be painful but a module IS available.

  • Unable to push because of large file deleted in the past
    2 projects | /r/git | 3 Jul 2023
    # git push origin feature-branch /usr/bin/gh auth git-credential get: 1: /usr/bin/gh auth git-credential get: /usr/bin/gh: not found /usr/bin/gh auth git-credential store: 1: /usr/bin/gh auth git-credential store: /usr/bin/gh: not found Enumerating objects: 9228, done. Counting objects: 100% (7495/7495), done. Delta compression using up to 8 threads Compressing objects: 100% (2090/2090), done. Writing objects: 100% (6033/6033), 72.77 MiB | 7.39 MiB/s, done. Total 6033 (delta 4402), reused 5194 (delta 3616) remote: Resolving deltas: 100% (4402/4402), completed with 477 local objects. remote: error: Trace: c1c90b47a5483929dcdd8c974a6c7d0695e86f67f680d8b88b80ef1c1bce74a remote: error: See for more information. remote: error: File deployment_20200220.sql is 872.78 MB; this exceeds GitHub's file size limit of 100.00 MB remote: error: GH001: Large files detected. You may want to try Git Large File Storage - To ! [remote rejected] rest-logging -> rest-logging (pre-receive hook declined) error: failed to push some refs to ''
  • What and Why, Git LFS?
    3 projects | | 12 Jun 2023
  • Coding your own AI in 2023 with fastai
    3 projects | | 27 Feb 2023
    Before commit we need to install git-lfs first, because our model.pkl file is too big. Follow the link and the instructions to install it for your operating system. Now we are able to use git-lfs for our model.pkl:

What are some alternatives?

When comparing nixpkgs and git-lfs you can also consider the following projects:

onedrive - OneDrive Client for Linux

git-fat - Simple way to handle fat files without committing them to git, supports synchronization using rsync

Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD

git - A fork of Git containing Windows-specific patches.

asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more

Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]

scalar - Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer

easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications

spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.

Bazel - a fast, scalable, multi-language and extensible build system

waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.

lakeFS - lakeFS - Data version control for your data lake | Git for data