nix3-store-verify(1)

⚠️ Warning

This program is experimental and its interface is subject to change. Like, don't build your whole personality around it, bestie β€” it might shift under you. 🫠


✨ Name

nix store verify β€” verify the integrity of store paths πŸ’–

πŸ“œ Synopsis

nix store verify [option…] installables…

πŸ“ Examples

  • Verify the entire Nix store:
# nix store verify --all
  • Check whether each path in the closure of Firefox has at least 2 signatures:
# nix store verify --recursive --sigs-needed 2 --no-contents $(type -p firefox)
# nix store verify --store https://cache.nixos.org/ \
  /nix/store/10l19qifk7hjjq47px8m2prqk1gv4isy-hello-2.10

πŸ’… Description

Okay so this command verifies the integrity of the store paths installables β€” or, if you pass --all, the entire Nix store. For every path, it checks that:

  • its contents match the NAR hash recorded in the Nix database; and
  • it is trusted, that is, it is signed by at least one trusted signing key, is content-addressed, or is built locally (β€œultimately trusted”).

πŸ”₯ Exit status

The exit status of this command is the sum of the following values:

  • 1 if any path is corrupted (i.e. its contents don’t match the recorded NAR hash).
  • 2 if any path is untrusted.
  • 4 if any path couldn’t be verified for any other reason (such as an I/O error).
Not me getting a 7 because everything went wrong at once 😭 it's a sum, bestie, they stack.

πŸŽ€ Options

  • --no-contents β€” Do not verify the contents of each store path.
  • --no-trust β€” Do not verify whether each store path is trusted.
  • --sigs-needed, -n n β€” Require that each path is signed by at least n different keys.
  • --stdin β€” Read installables from the standard input. No default installable applied.
  • --substituter, -s store-uri β€” Use signatures from the specified store.

🧠 Common evaluation options

  • --arg name expr β€” Pass the value expr as the argument name to Nix functions.
  • --arg-from-file name path β€” Pass the contents of file path as the argument name to Nix functions.
  • --arg-from-stdin name β€” Pass the contents of stdin as the argument name to Nix functions.
  • --argstr name string β€” Pass the string string as the argument name to Nix functions.
  • --debugger β€” Start an interactive environment if evaluation fails.
  • --eval-store store-url β€” The URL of the Nix store to use for evaluation, i.e. to store derivations (.drv files) and inputs referenced by them.
  • --impure β€” Allow access to mutable paths and repositories.
  • --include, -I path β€” Add path to search path entries used to resolve lookup paths.

This option may be given multiple times.

Paths added through -I take precedence over the nix-path configuration setting and the NIX_PATH environment variable.

  • --override-flake original-ref resolved-ref β€” Override the flake registries, redirecting original-ref to resolved-ref.
  • --commit-lock-file β€” Commit changes to the flake’s lock file.
  • --inputs-from flake-url β€” Use the inputs of the specified flake as registry entries.
  • --no-registries β€” Don’t allow lookups in the flake registries.
DEPRECATED β€” Use --no-use-registries instead.
  • --no-update-lock-file β€” Do not allow any updates to the flake’s lock file.
  • --no-write-lock-file β€” Do not write the flake’s newly generated lock file.
  • --output-lock-file flake-lock-path β€” Write the given lock file instead of flake.lock within the top-level flake.
  • --override-input input-path flake-url β€” Override a specific flake input (e.g. dwarffs/nixpkgs). The input path must not be empty. This implies --no-write-lock-file.
  • --recreate-lock-file β€” Recreate the flake’s lock file from scratch.
DEPRECATED β€” Use nix flake update instead.
  • --reference-lock-file flake-lock-path β€” Read the given lock file instead of flake.lock within the top-level flake.
  • --update-input input-path β€” Update a specific flake input (ignoring its previous entry in the lock file).
DEPRECATED β€” Use nix flake update instead.
  • --debug β€” Set the logging verbosity level to β€˜debug’.
  • --log-format format β€” Set the format of log output; one of raw, internal-json, bar or bar-with-logs.
  • --print-build-logs, -L β€” Print full build logs on standard error.
  • --quiet β€” Decrease the logging verbosity level.
  • --verbose, -v β€” Increase the logging verbosity level.

🌸 Miscellaneous global options

  • --help β€” Show usage information.
  • --offline β€” Disable substituters and consider all previously downloaded files up-to-date.
  • --option name value β€” Set the Nix configuration setting name to value (overriding nix.conf).
  • --refresh β€” Consider all previously downloaded files out-of-date.
  • --repair β€” During evaluation, rewrite missing or corrupted files in the Nix store. During building, rebuild missing or corrupted store paths.
  • --version β€” Show version information.

πŸ¦‹ Options that change the interpretation of installables

  • --all β€” Apply the operation to every store path.
  • --derivation β€” Operate on the store derivation rather than its outputs.
  • --expr expr β€” Interpret installables as attribute paths relative to the Nix expression expr.
  • --file, -f file β€” Interpret installables as attribute paths relative to the Nix expression stored in file. If file is the character -, then a Nix expression is read from standard input. Implies --impure.
  • --recursive, -r β€” Apply operation to closure of the specified paths.
Note β€” See man nix.conf for overriding configuration settings with command line flags.

okay babes that's the whole page, nothing skipped, every single flag accounted for πŸ’― go verify some store paths and feel like the main character πŸ‘‘

This was nix3-store-verify(1) from the Nix manual, section 1 β€” General Commands Manual. The footer is just the name itself, no date stamped on it, so consider this your official blessing: go off πŸ’œβœ¨

πŸ“¦ where this page comes from