mise

ID

mise

Home page

https://mise.jdx.dev

Version requirement

>= 2025.5.10

Platforms

🅱️ BSD · 🐧 Linux · 🍎 macOS · ⨂ Unix · 🪟 Windows

Operations

installed · outdated · search · install · upgrade · upgrade_all · remove · sync · cleanup · doctor

purl types

pkg:mise

CLI name

mise

Issues and PRs

📦 manager: asdf-based

Source

meta_package_manager/managers/mise.py

mise (formerly rtx) installs and switches between versions of developer tools like Node, Python, Ruby and any tool reachable through its plugin backends.

Note

mpm is system-scoped, so this wrapper reports every tool version present on disk regardless of which mise.toml (global or project) requested it. Project-pinned versions are not surfaced as a separate scope.

Note

Backend-prefixed tool IDs (pipx:ruff, cargo:ubi-cli, asdf:mise-plugins/mise-poetry) round-trip as-is. The colon is part of the package ID; mpm install pipx:ruff resolves the backend through mise itself.

Caution

mise outdated --json only reports tools tracked in a mise.toml (global or project). A tool installed bare with mise install <tool> and never pinned with mise use will not appear in the outdated list, so mpm outdated --mise understates the upgrade surface for those entries.

What mpm adds to mise

Through mpm, mise gains --exact search, to narrow results to exact names.

Bigger still, mpm reaches across every manager at once: mpm installed and mpm outdated cover mise alongside every other manager you run in one table, mpm upgrade --all updates them together, and mpm sbom exports the whole machine as one bill of materials.

Every mpm command also gains --dry-run and --plan previews, cross-scheme version comparison and purl identifiers. See manager augmentations for how each one is built.

Your mise commands, in mpm

You already know mise: each operation maps one-to-one onto mpm, in an interface shared by every manager.

To…

With mise

With mpm

List what’s installed

mise ls --installed --json

mpm --mise installed

List outdated packages

mise outdated --json

mpm --mise outdated

Search for a package

mise search --no-header --match-type contains node

mpm --mise search node

Install a package

mise install node@20

mpm install pkg:mise/node@20

Upgrade one package

mise upgrade node

mpm --mise upgrade node

Upgrade everything

mise upgrade

mpm --mise upgrade --all

Remove a package

mise uninstall --all node

mpm remove pkg:mise/node

Clear caches

mise cache clear

mpm --mise cleanup --cache

Run health checks

mise doctor

mpm --mise doctor

Prefix any command above with --dry-run to simulate the underlying manager calls without touching the system: the safe way to watch what mpm would do before trusting it.

Operations

Operation

Supported

Notes

installed

✓

outdated

✓

orphans

search

✓

exact search backfilled by mpm

install

✓

upgrade

✓

upgrade_all

✓

remove

✓

sync

✓

cleanup

✓

doctor

✓

Selecting and configuring mise

Deselect mise for a single run with --no-mise, or persist the choice in your configuration:

[mpm]
mise = false

Keep it enabled but tune how mpm drives it with a per-manager override:

[mpm.managers.mise]
timeout = 900

mpm config-template mise prints every overridable attribute as a ready-to-paste block.

Recipes

A few jobs you would otherwise script around mise, one mpm command each:

  • Snapshot and clone a machine: mpm --mise dump mise.toml, then mpm restore mise.toml on the next one.

  • Export a compliance SBOM: mpm --mise sbom (CycloneDX by default, --spdx for SPDX).

  • Gate CI on health: mpm --mise doctor relays mise’s own diagnosis and exits non-zero on trouble.

Privilege escalation

mpm runs this manager as the current user and never prepends sudo by default. Flip the policy for its privileged operations with --sudo or the per-manager sudo override.

See privilege escalation for the full policy.

Cooldown

State of mise’s release-age gating, from the cooldown support table:

  • Status: 🔜 Shipped upstream

  • Mechanism: minimum_release_age env MISE_MINIMUM_RELEASE_AGE / --minimum-release-age (default 24h)

  • Reference: mise settings

A cooldown only pays off where a compromised release can be withdrawn while the clock runs, and can only be emulated where the registry dates its releases. From the retraction table:

  • Registry: GitHub release assets

  • Retraction: None: withdrawing a build is the upstream author deleting their own release or tag. Nothing sits between them and the user

  • Publish date: ✅ server-set published_at on each release (REST API)

With --cooldown set, mpm skips this manager’s install and upgrade operations rather than run them unguarded (fail-closed); --allow-unsupported-managers opts back in.

Version probe

The version is probed by running:

$ mise --version
2026.6.3 macos-arm64 (2026-06-13)

and extracted with:

r"^(?P<version>\d+\.\d+\.\d+)"

Reference traces

Raw native outputs captured in the manager source: the reference mpm’s parsers were written against. If you know mise well and a transcript below looks wrong, or a newer release changed its output format, report it.

$ mise ls --installed --json
{
  "node": [
    {
      "version": "20.10.0",
      "install_path": "~/.local/share/mise/installs/node/20.10.0",
      "source": {"type": "mise.toml",
                 "path": "~/.config/mise/config.toml"}
    }
  ],
  "pipx:ruff": [
    {
      "version": "0.6.9",
      "install_path": "~/.local/share/mise/installs/pipx-ruff/0.6.9"
    }
  ]
}

$ mise outdated --json
{
  "node": {
    "requested": "20",
    "current": "20.0.0",
    "latest": "20.10.0"
  }
}

Feed any of these through mpm and the raw output becomes one uniform table, the same shape for every manager: filter it, project columns, or export it (mpm --mise installed --output json, or csv, toml, yaml), each package carrying a purl and a version comparable across managers.

Changelog

  • 6.6.0 (2026-06-17)

    • Add mise package manager (installed, outdated, search, install, upgrade, upgrade_all, remove, sync, cleanup), cross-platform; requires mise >=2025.5.10.