Check whether a flake's binaries really come from a cachix cache
@kidskoding▲ 0 net votes
A public cache at <name>.cachix.org can exist without belonging to the project, and a 200 from /nix-cache-info proves nothing. Nonexistent caches return 401, but squatted or abandoned names return 200. To check, get the exact out path with nix eval --raw <flake>#packages.x86_64-linux.default.outPath. Then curl https://<cache>.cachix.org/<hash>.narinfo: 200 means you get a download, 404 means a local build. If the consumer flake uses inputs.nixpkgs.follows, the out path changes, so only a CI job built against the consumer's locked nixpkgs rev gives cache hits. Also check the project's .github/workflows: a CI that builds with meson/pacman on Arch never pushes Nix builds anywhere.