Skip to main content

Globals audit

--globals lists your globally installed packages across npm, pnpm, yarn, bun and deno, and marks each one. Added in 1.1.0.

linux-cleanup --globals
linux-cleanup --globals -d 180
This mode never deletes anything

It prints copy-pasteable uninstall commands and stops. You decide what to run. Global packages are exactly the kind of thing that breaks a workflow when removed by surprise, so the tool refuses to remove them for you.

The verdicts​

VerdictMeaning
recently usedModified or accessed within --days. Leave it
needed by: <pkg>Another global declares it as a dependency. Removing it breaks that one
STALE — safe to uninstallIdle past the threshold and nothing else depends on it

"Safe to uninstall" means safe from the perspective of the other globals on your machine. It cannot know about a shell script, a CI job, or a habit of yours that calls the binary. Read the list before acting.

Why global packages matter here​

Globally installed packages are never deleted by any cleanup mode. ~/.local/share/pnpm, ~/.npm, ~/.yarn, ~/.bun/install/global and ~/.deno/bin are on the exact-match protected list specifically to keep them safe — a lesson from a real bug where the pnpm cleanup targeted the install root and wiped global packages. See 1.1.0.

This audit is the deliberate counterpart: visibility without automation.

Works without the package managers on PATH​

Each manager is queried through its CLI when available, and through filesystem inspection when not. So the audit still works on a machine where pnpm was installed but is not currently on PATH — which is often exactly the situation you are trying to diagnose.

If a runtime is on disk but not wired into your shell, --doctor is the mode that fixes that.

Good moments to run it​

  • Before reinstalling Node or switching version managers
  • Before migrating to a new machine — it is a portable inventory of your tooling
  • When npm ls -g output has become unrecognisable
  • Once or twice a year, as hygiene

Next​

  • Doctor — repair a runtime that is installed but not on PATH
  • Protected paths — why globals are never touched