As a custom package provider, you can host a scoped registry, so the location of your registry is available within Package Manager.
The intended scenario for scoped registries is to distribute custom packages within your organization, so your organization members can easily access packages (or collections of packages) within Package Manager.
Important
As a scoped registry provider, make sure any package registry servers you set up conform to Unity’s Terms of Service and Unity’s Package Guiding Principles & Guidelines.
Unity provides access to the Package Manager to facilitate sharing knowledge and creations, but not as a marketplace, store, or platform.
Don’t use the Unity Editor to promote, advertise, or distribute your packages, products, or services to members outside of your organization.
Hosting tools aren’t provided by Unity, but the Package Manager supports registries based on the npm protocol.
Important: When you set up your own package registry server:
/-/v1/search or /-/all endpoints.@scope notation that npm supports.If you want full control over who accesses packages in your scoped registry, you can enable npm authentication for specific users. Package consumers can then configure Scoped registry authentication to use their npm authentication tokens.