Docs menuWhat is LPM.dev?

What is LPM.dev Registry?

LPM.dev Registry is a hosted package registry for private, Free, Pool, and Marketplace packages. It hosts JavaScript and Swift packages under the @lpm.dev/* scope. It includes access control, licensing, author payouts, and team ownership.

LPM.dev Registry and LPM CLI

LPM CLI is the lpm executable that runs on your machine. It installs packages, writes lockfiles, manages workspaces, runs development tools, and connects to package registries.

LPM CLI works with several registries:

  • Packages outside @lpm.dev/* come from registry.npmjs.org by default.
  • LPM CLI reads private npm-compatible registries from .npmrc.
  • @lpm.dev/* packages go through LPM.dev Registry for access control, Pool attribution, and Marketplace licensing.

LPM.dev Registry is the hosted service. LPM CLI is the client that you use to work with it.

Private by default

Every package starts private. A publish does not list a package publicly or offer it for sale.

ModeWho can installHow authors earn
PrivateThe owner or members of the owning organizationNone
FreeAnyone, without an accountNone
PoolActive Pool subscribersUsage-based share of Pool subscription revenue
MarketplaceUsers or organizations with an active licenseDirect package sales

Free distribution needs a paid Pro or Organization plan. The move from Private to Free, Pool, or Marketplace is an explicit and permanent choice. After it, the package cannot return to Private or switch to another public mode.

What happens when you publish

When you publish, LPM.dev Registry validates the package identity and manifest and checks the declared ecosystem. After it accepts the version, background checks read the archive and compute the quality score.

Private and public distribution then follow different paths:

  1. Private versions become available to their owner or organization after the upload completes. They do not go through publication review or the public discovery pipeline.
  2. Free, Pool, and Marketplace versions wait for publication review. A successful upload does not make a version public. If an approved version already exists, consumers continue to get it. A package that moves from Private stays private until a release passes the review.
  3. Publication review reads the uploaded source, the lifecycle scripts, and the behavioral signals. It does not run package code. It approves a clean version. A suspicious version has a risk that is not an attack. The review approves it with a warning on the package page and in lpm audit. The review rejects a malicious version, and a version that it cannot judge waits for manual review. A separate skill review reads the Agent Skills a version ships.
  4. Approved public versions enter the enrichment pipeline. LPM.dev Registry can generate package summaries, API documentation, AI-readable context, and search metadata from the approved source.

A dependency check with the rules of the LPM Firewall can also reject a public version or add a warning.

Publication review decides whether consumers can install a public version. Enrichment helps people and tools understand the package. It does not decide publication, and it does not guarantee that the package has no defects.

Install packages

To install a package as a dependency, run lpm install:

lpm install @lpm.dev/acme.design-system

To copy the files of a source package into your project, run lpm add:

lpm add @lpm.dev/acme.login-form

To publish your own package, sign in and run lpm publish:

lpm login
lpm publish

The LPM CLI documentation describes installation behavior, registry configuration, command flags, lockfiles, and workspaces.

Hosted developer platform

LPM.dev Registry also has these hosted services:

  • Organizations give a team shared package ownership, member roles, shared licenses, tokens, webhooks, and audit logs.
  • Environments and secrets add encrypted cloud sync, organization sharing, deployment-platform pushes, and OIDC in CI to local secret storage.
  • Tunnels give local services public URLs, with claimed domains, access controls, and webhook inspection.

See also