Organization Packages

Organization packages use the organization's namespace as their Registry owner.

Package Identity

Set the package.json name to @lpm.dev/<organization>.<package>:

{
  "name": "@lpm.dev/acme-corp.design-system",
  "version": "1.0.0"
}

The owner portion must match the organization namespace:

Package: @lpm.dev/acme-corp.design-system
Page:    https://lpm.dev/acme-corp.design-system

The namespace cannot change after the organization owns a package.

Publish with LPM CLI

lpm login
lpm publish --check
lpm publish

There is no --org flag. LPM CLI uploads the package name from the project manifest, and the LPM.dev Registry resolves its owner and checks the authenticated account's organization role.

RolePublish organization packages
OwnerYes
AdminYes
MaintainerYes
MemberNo

lpm publish --check runs local package checks without verifying Registry authentication, organization membership, billing state, or whether the version already exists. See the LPM CLI publish reference for the complete client workflow.

New organization packages start private.

Access by Distribution Mode

ModeWho can install
PrivateCurrent organization members
PoolCurrent organization members and users with Pool access
MarketplaceCurrent organization members and customers covered by a purchased license

Private package contents are excluded from public AI analysis and embedding pipelines.

Moving a package to Pool or Marketplace queues its active versions for mandatory publication review. The package stays private until the activation version is approved. After public distribution activates, each new version is reviewed before subscribers or customers can install it.

While a public version is pending, organization members can access it and consumers continue receiving the highest approved version. See Distribution Modes for activation requirements, dependencies, and the permanent distribution choice.

Dashboard Management

Owners and admins manage organization packages from Dashboard > Organization > Packages. Depending on the package state, these controls include:

  • Package metadata and settings
  • Private, Pool, or Marketplace distribution
  • Marketplace pricing plans
  • Versions, deprecation, revocation, and archive controls
  • Security results, analytics, revenue, and publishing workflows

Marketplace payout providers are owner-only and are managed from the organization settings.

Maintainers can publish and use supported release-management operations, but dashboard settings and destructive package controls require an owner or admin. Members can view and install private organization packages without management access.

Organization publishing and private-package access are blocked after billing lapses beyond the grace period.

See Also