Arch Linux paru¶
- ID
paru- Home page
- Upstream stars
⭐ 8,939
- Last commit
2026-01-09
- Version requirement
>= 1.9.3
- Platforms
🅱️ BSD · 🐧 Linux · ⨂ Unix
- Operations
installed·outdated·orphans·search·install·upgrade·upgrade_all·remove·sync·cleanup·doctor- purl types
pkg:alpm·pkg:paru- CLI name
paru- Every call
paru --noconfirm --color never <command>- Issues and PRs
- Source
AUR helper wrapping pacman, driven through the paru binary.
Inherits every operation, parser and forced argument from Pacman; only
the binary and version probe differ. Its own --query --upgrades reports
AUR updates on top of the official repositories. The >=1.9.3 floor is the
first paru release to implement --sysupgrade, the flag the inherited
upgrade_all_cli builds.
Unlike pacman, the helper must run as the regular user: any transaction
building AUR packages aborts under root (can't install AUR package as root), and paru invokes sudo pacman itself for the privileged steps.
mpm therefore never wraps it in sudo.
What mpm adds to paru¶
Through mpm, paru gains:
a one-command
cleanup --orphansthat removes every orphaned dependency at once--extendedsearch, to match against package descriptions
Bigger still, mpm reaches across every manager at once: mpm installed and mpm outdated cover paru alongside pacaur, pacman, pamac, yay 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 paru commands, in mpm¶
You already know paru: each operation maps one-to-one onto mpm, in an interface shared by every manager.
To… |
With |
With |
|---|---|---|
List what’s installed |
|
|
List outdated packages |
|
|
Search for a package |
|
|
Install a package |
|
|
Upgrade one package |
|
|
Upgrade everything |
|
|
Remove a package |
|
|
List orphaned dependencies |
|
|
Clear caches |
|
|
Run health checks |
|
|
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 |
|---|---|---|
|
✓ |
|
|
✓ |
|
|
✓ |
|
|
✓ |
extended search backfilled by |
|
✓ |
|
|
✓ |
|
|
✓ |
|
|
✓ |
|
|
✓ |
|
|
✓ |
|
|
✓ |
Selecting and configuring paru¶
Deselect paru for a single run with --no-paru, or persist the choice in your configuration:
[mpm]
paru = false
The arguments and environment variables listed in the box atop this page are forced on every paru call, so runs stay quiet, non-interactive and reproducible: the defaults you would set in CI anyway.
Keep it enabled but tune how mpm drives it with a per-manager override:
[mpm.managers.paru]
timeout = 900
mpm config-template paru prints every overridable attribute as a ready-to-paste block.
Recipes¶
A few jobs you would otherwise script around paru, one mpm command each:
Snapshot and clone a machine:
mpm --paru dump paru.toml, thenmpm restore paru.tomlon the next one.Export a compliance SBOM:
mpm --paru sbom(CycloneDX by default,--spdxfor SPDX).Gate CI on health:
mpm --paru doctorrelays Arch Linux paru’s own diagnosis and exits non-zero on trouble.
Privilege escalation¶
Arch Linux paru runs sudo from inside its own commands: mpm never wraps it, keeps an already-warm credential cache alive for those internal escalations, and warns when a mutating call goes silent on a terminal with a cold cache, since a password prompt may be hiding in the stream.
See privilege escalation for the full policy.
Concurrency¶
mpm never runs paru at the same time as pacaur, pacman, pamac, pikaur, trizen or yay: they all reach the pacman database (/var/lib/pacman/db.lck), and two of them mutating at once fail to init their transaction. 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 Arch Linux paru’s release-age gating, from the cooldown support table:
Status: ❌ None (Arch AUR helper)
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: AUR
Retraction: None at the version level: an AUR package is a git repository with no per-version artifact to withdraw, so remediation is a maintainer push or deletion of the whole package
Publish date: ✅ server-set
LastModified, the push timestampmpm’syayoverlay gates on. Git commit dates are client-set (GIT_COMMITTER_DATE), forgeable, and never consulted
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:
$ paru --version
paru v1.10.0 - libalpm v13.0.1
and extracted with:
r"paru\s+v(?P<version>\S+)"
Upstream project¶
Metrics |
|
|---|---|
Activity |
|
Popularity |
|
Metadata |
|
Changelog¶
8.0.0.dev0(unreleased)Stop running the AUR helpers concurrently with
pacmanand with each other. All of them drive the same pacman database, either by shelling out tosudo pacmanor, forpamac, through Manjaro’s ownlibalpmbinding, so two mutating at once failed to init their transaction.
7.4.0(2026-07-25)The AUR helpers are no longer wrapped in
sudo: they refuse or break under root (makepkgrejects root builds, paru aborts AUR transactions, pacaur aborts its sync operations) and escalate through their own internalsudo pacmancalls, whichmpmnow tracks with theinternal_sudomarker (warm credential-cache keepalive, hidden-prompt watchdog). This also lets yay’s cooldown environment overlay reach the process, where thesudowrap used to strip it.
6.2.0(2026-03-25)Add
--color neveroption to all invocations.
5.3.0(2022-06-25)Add
parusupport.Run
install,upgrade,removeandcleanupoperations withsudo.