Frequently asked questions
Answers about getting started, pricing, the Pool, the Marketplace, private packages, and CI/CD.
General
What is LPM?
LPM is a package registry for JavaScript and Swift. Every package starts private. You can then sell it on the Marketplace, earn from its installs through the Pool, or, on Pro or Organization, make it Free for anyone to install. LPM CLI publishes your packages and installs them alongside your npm dependencies.
Is it compatible with npm, pnpm, Bun, and Yarn?
Yes. The LPM.dev Registry uses the npm registry API. Add the @lpm.dev scope to your project's .npmrc and a read token to ~/.npmrc. If you use LPM CLI, lpm setup local creates the token and writes the configuration for you. Yarn 2 and later don't read .npmrc, so they take the scope from .yarnrc.yml. A Free package needs no token.
How do I get started?
Install LPM CLI with npm install -g @lpm-registry/cli, run lpm login to sign in, then run lpm publish to publish your first package. The package starts private. Any plan, Hobby included, can move it to the Pool from the package's settings, and it goes public once a release passes security review.
Pricing and plans
How much does LPM cost?
LPM is free to start. The Hobby plan includes 2 private packages and 100 MiB of storage. Pro is $10/month with unlimited private packages, 5 GiB of storage, and a lower Marketplace fee. The Organization plan is $10/seat/month.
What are the platform fees for Marketplace packages?
The fee depends on the seller's plan when each payment is made: 15% of the price before tax on Hobby, 10% on Pro, and 10% on Organization. LPM takes it from each payment, renewals included, as a Stripe application fee.
The Pool
How does the Pool work?
Subscribers pay $12/month for unlimited installs from all Pool packages. 80% of each subscriber's payment goes to the authors of the Pool packages that subscriber installed that month. Each package counts once per subscriber a month, and a package installed as a dependency counts for less than one installed directly. If a subscriber installs none that month, LPM splits their share equally across all Pool packages.
Is opting into the Pool permanent?
Yes. Once you choose Pool distribution, the package can't go back to private, move to the Marketplace, or be deleted, even before its first release is approved. You can still archive or deprecate it.
Can organizations subscribe to the Pool?
Yes. The Owner and Admins turn on the Pool for each member, at $12/month per seat. A member with a seat can install every Pool package, and the seat's payment goes to authors the same way as a personal subscription.
Marketplace
How do I sell my packages?
Publish your package, connect a Stripe payout account, and add a pricing plan. Then choose Marketplace distribution in the package's settings. A plan can be a one-time price or a monthly or yearly subscription, priced per seat or for a whole organization. Buyers pay on the package page and install with lpm install.
How is the Marketplace different from the Pool?
On the Marketplace, you set the price and keep each sale minus the platform fee and Stripe's processing fee. In the Pool, subscribers pay $12/month for every Pool package, and authors share 80% of it by what each subscriber installs. Each package can be in only one of them, and the choice is permanent.
Can organizations buy licenses?
Yes. Sellers can offer two kinds of license. With an individual license, an organization buys a number of seats, and its Owner and Admins assign them to members at checkout or later. An organization license has a flat price and covers every current and future member.
Private registry and CI/CD
How many private packages can I have?
The Hobby plan includes 2 private packages with 100 MiB of storage. Pro includes unlimited private packages with 5 GiB of storage, and the Organization plan includes unlimited private packages with 5 GiB of storage per seat.
Can I make a private package public later?
Yes. Choose Free, Pool, or Marketplace distribution in the package's settings. The choice is permanent from the moment you make it, and the package can't go back to private or switch to another mode. It stays private until a release passes security review. Free distribution needs a paid Pro or Organization plan.
How do CI/CD tokens work?
Create a read or publish token in your personal or organization token settings, and store it as LPM_TOKEN in your CI provider's secrets. LPM CLI reads LPM_TOKEN directly. An organization token stops working when the member who created it leaves the organization or loses the Admin role. To publish from GitHub Actions or GitLab CI without a stored token, add a trusted publisher to the package.