Chromebrew¶

ID: chromebrew
Home page: https://chromebrew.github.io
Platforms: 🐧 Linux (ChromeOS only)
Operations: installed · search · install · upgrade · upgrade_all · remove · sync
purl types: pkg:chromebrew
CLI name: crew
Issues and PRs: 📦 manager: chromebrew
Source: meta_package_manager/managers/chromebrew.toml

Chromebrew is the package manager for ChromeOS, installing into /usr/local as the regular user.

Parsing notes, verified against the chromebrew master source (bin/crew, commands/list.rb, commands/search.rb, lib/const.rb):

crew must NOT run as root: bin/crew hard-aborts when Process.uid is zero, so no operation is marked sudo.
Output is colorized through HighLine (.lightgreen and friends) and crew does not honor the NO_COLOR environment variable: every operation passes its --no-color flag, which sits after the subcommand in crew’s docopt grammar.
crew list installed is name-only; the --verbose form adds the version column but injects a “Package”/“Version” header row and a “=======” separator. The installed regex requires a digit-led version so both decorations fall through.
No outdated: crew list states are available/compatible/incompatible/ essential/installed only, and crew upgrade computes AND applies upgrades, so there is no non-mutating upgradable listing. No cleanup either: CREW_DOCOPT has no clean verb.

What `mpm` adds to `chromebrew`¶

Through mpm, chromebrew gains --exact and --extended search, to narrow to exact names or match descriptions.

Bigger still, mpm reaches across every manager at once: mpm installed and mpm outdated cover chromebrew 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 `chromebrew` commands, in `mpm`¶

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

To…	With `chromebrew`	With `mpm`
List what’s installed	`crew list --verbose --no-color installed`	`mpm --chromebrew installed`
Search for a package	`crew search --no-color <query>`	`mpm --chromebrew search <query>`
Install a package	`crew install --no-color <package_id>`	`mpm install pkg:chromebrew/<package_id>`
Upgrade one package	`crew upgrade --no-color <package_id>`	`mpm --chromebrew upgrade <package_id>`
Upgrade everything	`crew upgrade --no-color`	`mpm --chromebrew upgrade --all`
Remove a package	`crew remove --no-color <package_id>`	`mpm remove pkg:chromebrew/<package_id>`

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 and extended search backfilled by `mpm`
`install`	✓
`upgrade`	✓
`upgrade_all`	✓
`remove`	✓
`sync`	✓
`cleanup`
`doctor`

Selecting and configuring `chromebrew`¶

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

[mpm]
chromebrew = false

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

[mpm.managers.chromebrew]
timeout = 900

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

Recipes¶

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

Snapshot and clone a machine: mpm --chromebrew dump chromebrew.toml, then mpm restore chromebrew.toml on the next one.
Export a compliance SBOM: mpm --chromebrew 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 needs root.

See privilege escalation for the full policy.

Cooldown¶

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

Status: ❌ None (Chrome OS)

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: Git-manifest indexes
Retraction: Index revert: reverting the manifest, Portfile or derivation commit withdraws the version
Publish date: ❌ only the commit date, which is client-set and trivially backdated

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:

$ crew version
1.75.0

and extracted with:

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

Reference traces¶

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

$ crew list --verbose --no-color installed
Package        Version
=======
less           643
nano           8.2

$ crew search --no-color {query}
less: GNU less is a paginator
lesspipe: Filters for less

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 --chromebrew installed --output json, or csv, toml, yaml), each package carrying a purl and a version comparable across managers.

Changelog¶

7.2.0 (2026-07-09)
- Add Chromebrew (crew) package manager with installed, search, install, upgrade, remove and sync support on ChromeOS; a bundled configuration-defined manager.