Distribution modes
Every LPM.dev Registry package starts private. Its owner can later choose Free, Pool, or Marketplace distribution. That choice is permanent from the moment the owner makes it.
Compare the modes
| Mode | Consumer access | Author revenue | Requirements | Can it change? |
|---|---|---|---|---|
| Private | Personal owner or organization members | None | Registry authentication | Yes, to Free, Pool, or Marketplace |
| Free | Anyone, without an account | None | Paid Pro or Organization plan, publication review, and dependency checks | No, once chosen |
| Pool | Pool subscribers | Share of the Pool author fund based on eligible usage | Publication review and dependency checks | No, once chosen |
| Marketplace | Customers covered by a purchased license | Package sales, less the applicable platform fee | Active payment provider, active pricing plan, publication review, and dependency checks | No, once chosen |
Free, Pool, and Marketplace packages are public packages. Everyone can see the package page of a public package, even without an account. The npm metadata is the package document that npm clients read. The mode decides who can read it and who can download the release archives:
| Mode | Package page and public versions | npm metadata | Release archives |
|---|---|---|---|
| Free | Everyone | Everyone | Everyone |
| Pool | Everyone | Any signed-in LPM.dev account | Pool subscribers |
| Marketplace | Everyone | Any signed-in LPM.dev account | Customers with a license |
The publisher is the owner, or a member of the owning organization. The publisher can also read the npm metadata and download the release archives.
Pool explains subscription revenue sharing. Marketplace explains pricing and customer licenses.
Before choosing public distribution
Publish at least one version of the package. Then, in the package dashboard, open Settings > Distribution & monetization.
Before you choose Marketplace, add at least one active pricing plan. The first Marketplace release becomes available only if the package then has an active pricing plan and an active payment provider.
When you choose, LPM.dev Registry checks the dependencies of the latest release. Earlier private versions stay private. A private dependency blocks public distribution. A Pool package cannot have Marketplace dependencies, and a Marketplace package needs the applicable redistribution rights for them. Dependencies has the complete rules.
Review and activation
If you choose Free, Pool, or Marketplace distribution, the package does not become public at once:
- LPM.dev Registry saves the choice, and you cannot change it after that. The package stays private.
- The latest eligible version goes through publication review.
- A clean result approves the release. A suspicious result approves it with a warning. If the review cannot judge the release, a person reviews it. A malicious result rejects the release.
- LPM.dev Registry checks publisher authority, dependencies, and the requirements of the chosen mode again before it makes an approved release available.
- The first release that passes every check makes the package available in the chosen mode. This step is activation.
The review can reject that release. You can also unpublish it before approval, or an administrator can quarantine it, which blocks it for everyone. In each case, the package keeps the mode you chose and stays private. Until a release is approved, the package counts toward the private package limit of your plan. To continue, publish a new version. It goes through the same review, and the first approved release makes the package available.
A release can pass its review and still wait for a requirement, such as an active payment provider for Marketplace. LPM.dev Registry checks such a release again automatically, and the release becomes available when the requirement is met. LPM.dev Registry checks it again soon after you connect a payment provider, add a pricing plan, renew your paid plan, or unarchive the package.
Earlier private versions stay visible only to the publisher. They do not go through review. They do not show in consumer metadata, version lists, or package pages. A signed-in publisher can preview an exact private version.
For example, you choose Pool while 2.0.0 is the latest version. The earlier private 1.0.0 stays hidden. After activation, you publish a 1.5.0 backport. It can become public after its checks pass. It does not replace 2.0.0 as the latest version.
The Distribution & monetization section shows what to do next. Until activation, it shows the release that is closest to activation. After activation, it shows the latest release.
Publishing after activation
Each new version of a Free, Pool, or Marketplace package goes through publication review before consumers can get it. While the review runs:
- The publisher can get that exact version.
- Consumers keep access to the approved versions.
- An install without a pinned version resolves to the highest approved version.
Publication review is the gate for each release. Quality scores, generated metadata, and Agent Skill processing are separate systems and do not replace it.
The choice is permanent
After you choose Free, Pool, or Marketplace, you cannot return the package to private or switch it to another distribution mode. You also cannot delete the package. These rules apply before the first release is approved and after a release is rejected. If the review finds a malicious release, LPM.dev Registry blocks only that release. The distribution of the package does not change. If you delete your account or organization, LPM.dev Registry also deletes each package that no approved release has made public yet.
You can still publish new versions and archive the package. You can also revoke, unpublish, and deprecate releases within the rules on Versioning.
Free publishing and hosting
Free is a distribution mode. It is separate from the account plans. A personal package needs a paid Pro plan to use Free distribution. An organization package needs a paid Organization plan. An unpaid trial does not qualify.
Before LPM.dev Registry makes a Free release available, it checks the LPM.dev Registry dependencies of the release. It reads declarations, aliases, bundles, source configuration, lockfiles, and Swift manifests. Each of these dependencies, direct or indirect, must be a Free package. Dependencies has the complete rules.
A Free release is permanent after it becomes public. You cannot revoke or unpublish it, even inside the 30-minute revocation window. To replace it, deprecate it and publish a corrected version. A release that is still in publication review can be revoked inside its window.
If the paid plan ends, existing Free releases stay downloadable. After 30 days, LPM.dev Registry deprecates the package automatically. It also schedules the removal of the hosted files for 365 days after the plan ends. Both periods start when the paid plan ends. After a cancellation, that is the end of the last paid period.
If you renew before the removal, LPM.dev Registry clears the automatic schedule. A renewal does not clear a deprecation that you set, or a security restriction. A removal keeps the package name and its version records, so nobody else can use the name. A later renewal cannot restore removed files.
Security rescans continue after the paid plan ends. If a dependency is quarantined, LPM.dev Registry also blocks each known release that contains its files. This includes files in nested bundles. To replace an affected release, publish a corrected version.
Software licenses
The distribution mode does not change the software license of your package. LPM.dev Registry enforces package access, purchases, and dependency entitlement rules. It does not decide if your license terms are legally compatible with paid distribution or redistribution.
Choose license terms that match how customers will use and redistribute the package.