, the same developer behind :
mise use -g aube
It is also available via Homebrew (brew install endevco/tap/aube) and npm (npm install -g --ignore-scripts=false @endevco/aube).
Inside an existing Node.js project, just run:
aubr test
Aube will install dependencies if needed and then run the script. No migration step, no lockfile conversion.
Daily commands
aube add react # add a dependency
aube add -D vitest # add a dev dependency
aube remove react # remove a dependency
aube update # update within package.json ranges
aubr build # run a script, auto-installing if needed
aube test # run tests, auto-installing if needed
aubx cowsay hi # run a one-off tool
aube install # install only (setup, Docker, CI)
aube ci # clean, frozen install for CI
You can also run scripts directly:
aube dev
aube build
aube lint
If the script exists in package.json, aube treats that as aube run <script>.
Audit
Aube has a built-in audit command that uses the same advisory data source as npm audit and pnpm audit:
aube audit # list known CVEs at low+ severity
aube audit --audit-level high
aube audit --fix # write package.json overrides to patched versions
aube audit --json | jq # machine-readable for CI
When to use it
Aube is worth trying if you want faster installs without changing your team's workflow. The lockfile compatibility means you can use it locally while your CI and teammates continue with pnpm, npm, or Yarn. The security defaults are the most aggressive of any Node.js package manager I have seen, and paranoid: true adds a lifecycle-script jail when you want the stricter bundle.
The project is young (v1.x, MIT-licensed, on GitHub) but moving fast. If you are already using Mise, the install is one command away.
SOCIAL SHARE CARD GENERATOR