mise trust
- Usage:
mise trust [FLAGS] [CONFIG_FILE] - Effect: modifies state
- Source code:
src/cli/trust.rs
Mark a config file as trusted
Trust lets mise load the parts of a config file that can run code or change your environment. Without it, mise prompts, skips the file, or fails with an untrusted-config error when it cannot prompt.
A file with no template syntax that contains only min_version, [tools] entries with plain version strings (or arrays of them), and [tasks] in which no task lists secrets does not need trust unless paranoid mode is on. Commands that run project code (mise run, task shorthand such as mise build, mise install, mise exec, mise watch, and mise daemons start|restart|register) trust their active config automatically.
Trusting a config file in a repository's main checkout also trusts the same path in its git worktrees. Paranoid mode (https://mise.jdx.dev/paranoid.html) turns off automatic and worktree trust and requires trust, tied to the file's contents, for every config outside the global and system config. See https://mise.jdx.dev/security.html#configuration-trust
Arguments
[CONFIG_FILE]— The config file whose trust status to change
Flags
-a --all— Trust all config files in the current directory, its parents, and its subdirectoriesSubdirectories are walked respecting .gitignore, skipping hidden directories and common build and dependency directories (node_modules, vendor, target, dist, build).
--ignore— Do not trust this config and ignore it in the future--show— Show the trust status of config files in the current directory and its parentsDoes not trust or untrust any files.
--untrust— Remove explicit trust for this config-h --help— Print help
Examples
Trust the nearest untrusted config in this directory or a parent
mise trustTrust a specific file
mise trust ~/src/app/mise.tomlList configs here and above with their trust status
mise trust --show