LPM CLI

A package manager for every registry

Use the LPM CLI in place of npm, pnpm, Yarn or Bun. It installs from npm and from your private registries, and its local tools need no LPM account.

LPM CLI
npm install -g @lpm-registry/cli

Use it like the package manager you have

The LPM CLI installs the packages you already use, from the registries you already use.

Works with every registry

The LPM CLI installs npm packages straight from the npm registry, and reads your .npmrc for private registries. Only @lpm.dev packages come from LPM.dev.

Switch from npm, pnpm, Yarn or Bun

lpm migrate converts your project and imports its lockfile. Preview the change with --dry-run, and undo it with --rollback.

Fast installs

In our benchmark, the LPM CLI installed a T3 app from a cold cache in 1.6 seconds, with less peak memory than Bun, pnpm or npm.

Configured per machine or per project

Set your defaults once with lpm config, and override them for one project in lpm.toml. lpm config list shows each setting's value and where it comes from.

Know what you install

Dependency scripts wait for your approval, and the approved ones run in a sandbox.

Scripts in a sandbox

Dependency scripts wait for your approval. An approved script then runs in an operating-system sandbox, with a restricted filesystem and a filtered environment.

Guarded settings

A project can't quietly turn its protections down. A setting that weakens them, such as switching the sandbox off, is rejected until you approve it yourself, for a limited time.

Query your dependencies

lpm query finds the packages in your tree by what they do, such as running eval or starting child processes. Add --assert-none, and the same selector fails a CI job.

See why a package is there

lpm graph draws your dependency tree, in the terminal or as an interactive page. lpm why shows every path from your project to one package.

Sigstore provenance

A release published with provenance carries a Sigstore attestation of the repository, workflow and commit that built it. The LPM CLI can refuse a package whose attestation fails.

Licenses and SBOMs

lpm licenses lists the license of every installed dependency, and can fail a build on copyleft, missing or denied licenses. lpm sbom writes a bill of materials in SPDX or CycloneDX.

Run, lint, test and serve

A task runner with a cache, plus lint, format, tests and a dev server.

Tasks that skip finished work

lpm run runs your tasks in dependency order. Turn on caching for a task, and the LPM CLI restores its outputs when nothing it depends on has changed.

Monorepos

Workspaces share one lockfile and link their local packages. Filter a command to some members, or run it only for the ones a change affects.

Lint, format and pin Node

lpm lint runs Oxlint, lpm fmt runs Biome, and lpm use node@22 installs and pins a Node.js version. The LPM CLI downloads each tool on first use, so a new project needs no setup.

One command for every service

List your services in lpm.json, and lpm dev starts them in order. A service waits until the ones it depends on are ready, and gets their URLs and ports in its environment.

Local HTTPS

lpm dev --https serves your app over HTTPS that your browser trusts. lpm cert creates the local certificate authority and adds it to your machine's trust store.

Local hostnames

Give each service a hostname such as app.test. The LPM CLI's local proxy serves it over HTTPS and forwards to the service's port, and lpm dev adds the name to your hosts file.

Publish, copy and share

The same binary publishes your packages, copies source into a project and installs Agent Skills.

Publish to several registries

One lpm publish can send a package to lpm.dev, npm and GitHub Packages, each under its own name. From GitHub Actions or GitLab CI it needs no stored token, and it can attach signed provenance.

Copy source into your project

lpm add copies a package's source files into your project, where you can edit them. It works for packages from lpm.dev, npm or a private registry, and adds no dependency.

Install Swift packages

lpm install adds a Swift package to your Package.swift, or to an Xcode project that has none, and resolves it with Swift Package Manager. It sets up the registry the first time a project needs it.

Skills for every agent

lpm skills installs Agent Skills from a package, a GitHub repository or a local folder, for one project or for your whole machine. It links each skill into the agents you choose, and one command updates them.

Hosted services, when you want them

The remote cache, tunnels, LPM Firewall and encrypted env sync run on LPM. They need an account on Pro, at $10 a month, or on Organization.

Remote cachePro and Organization

The remote cache shares finished task results between your machines and your CI jobs. A task that already ran somewhere with the same inputs is restored, with its outputs and its logs.

Included
25 GiB on Pro, and 25 GiB for each seat on Organization.
Kept for
14 days after a result's last use.
If it fails
The task runs on your machine. A cache problem never fails a build.
In CI
A token can read the cache without being able to write to it.
Read the remote cache docs

TunnelsPro and Organization

lpm tunnel 3000 gives a local server a public HTTPS URL. The LPM CLI opens the connection from your machine, so you open no inbound port.

Included
3 tunnels at once and 100,000 requests in each billing period on Pro. On Organization, each seat adds 100,000 requests.
Your URL
On Pro, it stays the same in every session. A Pro account or an organization can also claim 3 stable domains, such as acme-api.lpm.llc.
Webhooks
The LPM CLI records each request, so you can inspect it and replay it to your server.
Access
--tunnel-auth rejects requests that don't carry the session's token.
Read the tunnel docs

LPM FirewallPro and Organization

Turn LPM Firewall on, and the LPM CLI asks for a verdict on each public npm version it's about to install, the dependencies of your dependencies included.

Modes
monitor reports what it would block. enforce waits for each verdict, and a block stops the install.
Evidence
Each finding has a public report on firewall.lpm.dev, with the flagged lines of code.
Your packages
They still download from npm. The lookup sends the names, versions and hashes of public npm packages only.
Coverage
A version with no verdict yet is unknown, which is not the same as clean.
See the public reports

Encrypted env syncPro and Organization

lpm env push encrypts a project's secrets on your machine, and lpm.dev keeps the encrypted copy.

Without sync
lpm env keeps a project's values on your machine and out of the repository, on every plan.
Your scripts
lpm dev and lpm run load the values into your scripts.
Teams
In an organization, each member with access gets the project's key encrypted for that member alone.
Deploys
Push an environment to Vercel, Coolify, Fly.io, Railway or GitHub Actions.
More about secrets

Frequently asked questions

Do I need an LPM account?

No. Installs, the task runner, the built-in tools, local HTTPS and local secrets work without one. Tunnels, the remote cache, LPM Firewall and encrypted env sync need an account on Pro or Organization.

Does it install from npm, or from lpm.dev?

From npm. Ordinary packages come straight from registry.npmjs.org, and a registry in your .npmrc is used as written. Only @lpm.dev packages come from the LPM.dev Registry.

Can I try it on a project I already have?

Yes. lpm migrate --dry-run shows what would change. lpm migrate imports your npm, pnpm, Yarn or Bun lockfile, and lpm migrate --rollback undoes it.

My build needs a postinstall script. What happens?

The install finishes and lists the scripts it blocked. Approve the package with lpm approve-scripts, and lpm rebuild then runs its script in the sandbox.

Which platforms have a binary?

macOS on Intel and Apple silicon, Linux glibc on x64 and ARM64, Linux musl on x64, and Windows on x64 and ARM64.

Is the LPM CLI open source?

Yes, under MIT or Apache-2.0. The hosted services, such as the remote cache and tunnels, are not open source.

Try it on a project you already have

Install the LPM CLI, then run lpm migrate --dry-run to see what would change before anything does.

LPM CLI
npm install -g @lpm-registry/cli