Skip to content
v2.2.12 Release notes

A package manager for Node.js

Skip the install step.

aube installs missing or stale dependencies before running your scripts, shares packages across projects, and keeps your existing lockfile.

mise use -g aube
~/your-projectterminal

$ aubr build

Dependencies changed. Installing first…

✓ Dependencies ready

$ vite build

✓ Build complete

$ aubr build

Dependencies unchanged. Straight to your script.

$ vite build

✓ Build complete

Illustrative output. Same command, one less step to remember.

Your project. Your lockfile.

Less setup, more doing

Start with the command you need.

Familiar files

Keep the lockfile.
Try a different workflow.

aube reads and writes supported pnpm, npm, Yarn, and Bun lockfiles in place. Try it locally, review the diff, and run your tests before switching the team.

Check format compatibility
Shared storage

Same dependencies.
Less duplicated work.

Package files live in a content-addressable store. The global virtual store also shares package directory trees across local projects and worktrees.

Understand the store
Explicit build policy

Know what runs
during an install.

Dependency scripts need project approval or built-in trust. Explicit denies win. Optional build jails restrict approved scripts, with enforcement that depends on your OS.

Review dependency builds
Checks during resolution

Look beyond
the version number.

aube checks publishing evidence, release age, and known malicious packages when selecting versions. Each check has documented defaults and exceptions.

Read the security model

Measured, with context

A shorter wait
for a fresh install.

Warm cache, committed lockfile, no node_modules. These are recorded results for the same fixture using each tool’s default install model.

All scenarios and methodology

Warm install · seconds · lower is better

aube0.19 s
bun0.61 s
pnpm1.52 s
npm3.70 s

aube’s global virtual store is enabled; pnpm’s is at its default of off.