LPM.dev Registry

One registry for private, free and paid packages

Every package starts private. Release it as Free, earn from the Pool or sell it on the Marketplace. LPM reviews every public version before anyone can install it.

Four ways to distribute a package

A package is private until you choose how it goes public. The choice is yours for each package.

Learn more

Checked, documented and found by agents

Every publish runs quality checks, and a public release gets a security review and API docs. AI agents in any editor that supports MCP can find your package.

More in every package

Agent Skills travel with a package, its API docs are written for you, and Swift packages install through Swift Package Manager.

Package skills

Authors ship Agent Skills with their package. lpm install writes them into your project, where your coding agent can read how to use it.

API docs, written for you

After a public release, LPM writes the package's API documentation from its type declarations. Every export gets a page.

A registry for Swift packages

Swift Package Manager installs LPM packages natively. LPM signs every Swift release, and Swift Package Manager checks the signature on download. A Swift package can be private, Free, in the Pool or on the Marketplace.

Show who publishes, and protect what you publish

Prove your domain and your npm account. Guard your account with a passkey, and your releases with alerts.

Verified domain

Prove you control your domain with one DNS record. It then shows on your profile, your package pages and your package cards.

Prove your npm account

Run lpm verify-npm to prove you own your npm account. Your profile shows it, and if LPM is holding your npm username, it becomes yours.

Passkeys and 2FA

Protect your account with a passkey on your device or a code from an authenticator app. LPM asks for it again before sensitive actions, such as creating a token.

Publish anomaly alerts

LPM emails you when a publish doesn't look like yours, such as one from a new country, or one made with a token on a package that publishes from CI. Approve the release, or quarantine it and revoke the token.

Revoke a release

Published the wrong build? Revoke the release within 30 minutes, before anyone else installs it, then publish that version number again.

Enterprise features. Indie pricing.

Roles, audit logs, webhooks and analytics for teams that publish private packages. $10 per seat a month, with no sales call.

Learn more

Team roles

Members install private packages, Maintainers publish, Admins manage members and settings, and only the Owner handles billing.

CI and deploy tokens

Scope each token to read or publish, and to one package or tag if you like. A trusted publisher lets GitHub Actions or GitLab CI publish with no stored token.

Audit logs

Publishes, invitations, and member, token and settings changes. The Owner and Admins can search the log and filter it by action and date.

Required identity provider

Require every member to connect an account from one provider: GitHub, Google, GitLab, or Bitbucket.

Webhooks

Get a request when a package is published, a member joins or a token is created.

Analytics

Daily downloads, installers and top versions for each package, next to your revenue.

The rest of your dev loop

The same account runs LPM Firewall, a remote cache, tunnels and encrypted env sync through the LPM CLI, on Pro and Organization.

Learn more

LPM Firewall

Turn it on, and the LPM CLI asks for a verdict on each public npm version it's about to install. In enforce mode, a block stops the install. The evidence for each verdict is public on firewall.lpm.dev.

Learn more

Remote cache

The remote cache restores finished task results on the next laptop or CI job with the same inputs. Pro includes 25 GiB, kept 14 days after last use.

Learn more

Tunnels

lpm tunnel 3000 gives a local server a public HTTPS URL that stays the same every session. The LPM CLI records each request, so you can inspect it and replay it.

Learn more

Secrets, encrypted before they leave

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

Learn more

LPM Vault

Keep secrets out of .env files on a Mac. LPM Vault stores them in your Keychain, keeps a history of every change, and publishes an environment to the platform that runs your app.

Learn more

Frequently asked questions

Does LPM replace npm?

No. The LPM.dev Registry hosts @lpm.dev packages. Your other packages keep coming from the npm registry, or from the registry your .npmrc names.

Is a package public when I publish it?

No. Every package starts private. It stays private until you choose Free, the Pool or the Marketplace, and until one of its releases passes the security review.

What does the security review check?

It runs checks on the release's files, an AI security model that decides the verdict, and a check of the release's dependencies. A clean release is released. A suspicious one is released with its findings shown. A malicious one is rejected. Private releases are not reviewed.

Can npm, pnpm, Yarn or Bun install LPM packages?

Yes. npm, pnpm, Yarn 1 and Bun install @lpm.dev packages through a scoped .npmrc. Yarn 2 and later read the same scope from .yarnrc.yml. Every package except a Free one also needs a read token.

Does the registry host Swift packages?

Yes. The LPM.dev Registry implements the Swift Package Registry API, so Swift Package Manager resolves LPM packages natively. LPM signs every Swift release.

What does it cost?

Hobby is free, with 2 private packages and 100 MiB of storage. Pro costs $10 a month, and Organization costs $10 per seat a month. Publishing to the Pool and the Marketplace is open to every plan.

Publish your first package

The Hobby plan is free, and signing up needs no credit card. It includes 2 private packages, and it can publish to the Pool and the Marketplace.