Becoming a Pool Author

Promote a private LPM.dev Registry package to the Pool to make its approved versions available to every Pool subscriber and earn a share of settled subscription revenue.

Before you request Pool distribution

The package must have at least one published version. Its active versions must also satisfy the public-distribution dependency rules:

DependencyPool package rule
Another Pool packageAllowed
Private LPM.dev Registry packageBlocked, including packages with the same owner
Marketplace packageBlocked in every dependency relation, including bundles and same-owner packages; Pool subscribers must not need a separate purchase
Package from another registryNot blocked by the LPM.dev Registry distribution check; its access and license terms still apply

The LPM.dev Registry checks active dependencies, devDependencies, peerDependencies, and bundled dependencies during promotion. A bundle declaration or Commercial License does not make a Marketplace dependency valid for Pool. If dependency rights change while review is pending, activation can be cancelled and must be requested again after the conflict is resolved.

Request review

  1. Open the package in the Dashboard.
  2. Go to Settings > Distribution.
  3. Select Pool.
  4. Confirm the permanent distribution change.

The package does not become public immediately. The LPM.dev Registry:

  1. Keeps the package in private distribution.
  2. Queues its active versions for public-distribution review.
  3. Rechecks dependency eligibility before activation.
  4. Activates Pool distribution after the promotion version is approved.

Each version becomes available to subscribers only after its required review is approved. Future versions of an active Pool package follow the same publish-and-review boundary.

See Publishing for the upload flow and Package Distribution for review outcomes.

Permanent distribution and package lifecycle

After activation, Pool distribution is permanent:

  • The package cannot return to private distribution.
  • The package cannot switch to Marketplace or set package-specific pricing.
  • The package cannot be deleted.
  • The package can be archived and later unarchived from Package > Danger Zone.

Archiving removes the package from new discovery and distribution without changing its Pool mode.

The Danger Zone can also deprecate the whole package or an individual version with a message. Deprecated versions remain installable and warn consumers, making deprecation the normal choice when users should migrate to a replacement.

A Pool version can be unpublished only while it is less than 72 hours old and has no external installs. After either boundary is reached, use deprecation instead.

How earnings are allocated

Pool earnings are based on each subscriber's eligible package observations, not raw download-event volume.

  • A subscriber/package pair is recorded at most once per billing period.
  • Direct observations have weight 1.00.
  • Pool dependencies use depth weights 0.70, 0.49, and 0.34.
  • The two-unique-installer rule applies only to dependency observations.
  • A dependency with the same owner as the directly downloaded package receives 30% of its normal weight.

See Revenue Sharing for the full calculation.

Use LPM CLI to inspect current-period estimates for personal and organization-owned packages available to your account:

lpm pool

The output includes weighted downloads, estimated earnings, and a per-package breakdown. Estimates can change until the billing period is calculated. See the LPM CLI pool reference for command and JSON output.

Configure payouts

You can begin accruing Pool earnings before connecting Stripe. Configure an active Stripe payout account before you want above-threshold earnings transferred:

  • Personal packages: Dashboard > Settings > Payout Settings
  • Organization packages: Organization > Settings > Payout Settings; organization owners manage payout accounts

The LPM.dev Registry calculates the previous billing period on the 1st of the month and attempts eligible payouts on the 5th:

  • The minimum payout is $10 across an owner's combined pending Pool earnings.
  • Earnings below the threshold carry forward.
  • Above-threshold earnings without an active payout account remain pending.
  • After an eligible account is connected, pending setup payouts are retried automatically.
  • Payouts are made in USD through Stripe.

See also