Mamba¶

ID: mamba
Links: Home page · Documentation · Repository
Upstream stars: ⭐ 8,100
Last commit: 2026-09-25
Version requirement: >= 2
Platforms: 🐧 Linux · 🍎 macOS · 🪟 Windows
Operations: installed · outdated · search · install · upgrade · upgrade_all · remove · cleanup
purl types: pkg:conda/ · pkg:mamba/
CLI name: mamba
Issues and PRs: 📦 manager: conda-based
Source: mamba.py

Conda-compatible package manager, reimplemented in C++.

Reaches the same channels conda does, resolving with libsolv behind a command line of its own rather than delegating to conda. It is wrapped on the same grounds as nala over apt: same archives, separate implementation. Since 2.0 it shares no code with conda at all, the Python executable of the 1.x line having been replaced by a dynamically linked build of micromamba.

Important

Every operation targets mamba’s currently active environment, which is base when none is activated. mpm neither activates nor switches environments: it inspects and mutates whatever mamba resolves from the inherited CONDA_PREFIX / CONDA_DEFAULT_ENV, exactly as a bare mamba call in the same shell would, and exactly as the conda wrapper does. Per-environment targeting is not supported yet.

What `mpm` adds to `mamba`¶

Through mpm, mamba gains --extended search, to match against package descriptions.

Bigger still, mpm reaches across every manager at once: mpm installed and mpm outdated cover mamba alongside conda, micromamba, pixi and any 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 `mamba` commands, in `mpm`¶

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

To…	With `mamba`	With `mpm`
List what’s installed	`mamba list --json`	`mpm --mamba installed`
List outdated packages	`mamba update --all --dry-run --json`	`mpm --mamba outdated`
Search for a package	`mamba search "zstd" --json`	`mpm --mamba search <pkg>`
Install a package	`mamba install --yes zstd`	`mpm install pkg:mamba/zstd`
Upgrade one package	`mamba update --yes zstd`	`mpm --mamba upgrade zstd`
Upgrade everything	`mamba update --all --yes`	`mpm --mamba upgrade --all`
Remove a package	`mamba remove --yes zstd`	`mpm remove pkg:mamba/zstd`
Clear caches	`mamba clean --all --yes`	`mpm --mamba cleanup --cache`

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`	✅	Extended search backfilled by `mpm`.
`install`	✅
`upgrade`	✅
`upgrade_all`	✅
`remove`	✅
`sync`	❌	Nothing in the command set refreshes the index on its own; the conda wrapper implements none either, so this is parity rather than a gap.
`cleanup`	✅
`doctor`

Configuration¶

Ignore mamba on the mpm CLI by passing the --no-mamba option.
Ignore it for every run in your configuration:
```
[mpm]
mamba = false
```
Raise the timeout of all mamba calls:
```
[mpm.overrides.mamba]
timeout = 900
```

Run mpm config-template mamba to print all overridable settings for your configuration file:

[mpm.overrides.mamba]
cli_names = [
    "mamba",
]
cli_search_path = []
dry_run = false
ignore_auto_updates = true
plan = false
post_args = []
pre_args = []
pre_cmds = []
requirement = ">=2.0.0"
stop_on_error = false
unmaintained = false
version_cli_options = [
    "--version",
]
version_regexes = [
    "^(?P<version>\\d+\\.\\d+\\.\\d+\\S*)$",
]

Recipes¶

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

Snapshot and clone a machine: mpm --mamba dump mamba.toml, then mpm restore mamba.toml on the next one.
Export a compliance SBOM: mpm --mamba sbom (CycloneDX by default, --spdx for SPDX).

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.

None of its operations is privileged.

See privilege escalation for the full policy.

Concurrency¶

mpm never runs mamba at the same time as conda or micromamba: they act on one environment prefix and one package cache, and conda honors none of the locks mamba takes on them. Each mutating operation waits for the previous one, even with a higher --jobs, while managers outside this group keep running in parallel.

Only mutations are held back. The read-only queries (installed, outdated, search) take no backend lock and stay fully concurrent.

Cooldown¶

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

Status: ❌ None on the CLI (libmambapy API shipped in mamba 2.9.0)
Mechanism: exclude_newer_timestamp, libmambapy only
Reference: mamba-org/mamba#4228

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: anaconda.org / conda-forge (pkg:conda)
Retraction: Relabel: “we do not allow edits or the deletion of packages on conda-forge” (immutability); a bad artifact is labelled broken and “Users will no longer be able to install them by default” (procedure)
Publish date: ✅ upload_time, with the broken label carried in labels (API)

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

Reference traces¶

A collection of raw native outputs captured from the manager’s own CLI and recorded in the manager source. If you know Mamba well and a transcript below looks wrong, or a newer release changed its output format, report it.

$ mamba list --json
{
    "log_history": [],
    "packages": [
        {
            "base_url": "https://conda.anaconda.org/conda-forge",
            "build_number": 2,
            "build_string": "h23cfdf5_2",
            "channel": "conda-forge",
            "dist_name": "libiconv-1.18-h23cfdf5_2",
            "md5": "4d5a7445f0b25b6a3ddbb56e790f5251",
            "name": "libiconv",
            "platform": "osx-arm64",
            "url": "https://conda.anaconda.org/conda-forge/osx-arm64/libiconv-1.18-h23cfdf5_2.conda",
            "version": "1.18"
        }
    ]
}

$ mamba update --all --dry-run --json
{
    "actions": {
        "LINK": [
            {
                "build": "h23cfdf5_2",
                "fn": "libiconv-1.18-h23cfdf5_2.conda",
                "name": "libiconv",
                "version": "1.18"
            }
        ],
        "PREFIX": "/opt/conda",
        "UNLINK": [
            {
                "build": "h23cfdf5_1",
                "fn": "libiconv-1.17-h23cfdf5_1.conda",
                "name": "libiconv",
                "version": "1.17"
            }
        ]
    },
    "dry_run": true,
    "log_history": [],
    "prefix": "/opt/conda",
    "success": true
}

$ mamba update --all --dry-run --json
{
    "dry_run": true,
    "log_history": [],
    "message": "All requested packages already installed",
    "prefix": "/opt/conda",
    "success": true
}

Version check¶

The version is probed by running:

$ mamba --version
2.9.0

and extracted with:

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

Upstream project¶

Metrics	`mamba-org/mamba`
Activity
Popularity
Metadata

Changelog¶

8.0.0 (2026-09-20)
- Resolve pkg:alpm, pkg:conda, pkg:deb, pkg:melpa, pkg:pypi and pkg:rpm pURLs to these managers too, alongside the ones already handling each type.
- Add mamba and micromamba, reading the inventory from list --json and synthesizing outdated from the dry-run transaction the way the conda wrapper does. Search matches package names exactly.
- Stop running conda, mamba and micromamba concurrently: they act on one environment prefix and one package cache.
- Record that each tool’s shipped release-age gate never reaches the commands mpm drives, in place of a pending upstream proposal.