About organization scopes and packages

Every organization is granted an organization scope, a unique namespace for packages owned by the organization that matches the organization name. For example, an organization named "wombat" would have the scope @wombat.

You can use scopes to:

• Maintain a fork of a package: @wombat/request.
• Avoid name disputes with popular names: @wombat/web.
• Easily find packages in the same namespace

Packages in a scope must follow the same naming guidelines as unscoped packages.

Managing unscoped packages

While you are granted a scope by default when you create an organization, you can also use organizations to manage unscoped packages, or packages under a different scope (such as a user scope).

Edit this page on GitHub

1 contributor

Last edited by mona on March 21, 2023

声明：npm 及相关 logo 的版权归 npmjs.com 所有。本站点仅用于 npm 中文文档，与 npmjs.com 没有任何关系。由于译者水平有限，且避免产生误解，条款和政策内容不进行翻译，关于这部分，请移步官网查看最新内容。