gat-bypass-2fa-docs
@reggi/path-to-regexp
dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2
dependabot/npm_and_yarn/main/eslint-10.4.0
dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0
dependabot/npm_and_yarn/main/proc-log-7.0.0
dependabot/npm_and_yarn/npm_and_yarn-826852524d
dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2
deprecate-totp-2fa
dhei/classic-tokens
gat-bypass-2fa-docs
jpg619/fix-accessibility-content-flow
jpg619/version-bump-tar-2
kartykp/gat-bypass-2fa-docs
kartykp/upgrade-path-to-regex
main
maitxn/version-bump-tar
patch-1
reggi/cache-based-on-version
reggi/dev-engines
reggi/fix-transform-prettier
reggi/overrides
update-search-sensitivity
| 1 | --- |
| 2 | title: About organization scopes and packages |
| 3 | redirect_from: |
| 4 | - /about-org-scopes-and-packages |
| 5 | --- |
| 6 | |
| 7 | 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`. |
| 8 | |
| 9 | You can use scopes to: |
| 10 | |
| 11 | - Maintain a fork of a package: `@wombat/request`. |
| 12 | - Avoid name disputes with popular names: `@wombat/web`. |
| 13 | - Easily find packages in the same namespace |
| 14 | |
| 15 | Packages in a scope must follow the same [naming guidelines][name-guidelines] as unscoped packages. |
| 16 | |
| 17 | ## Managing unscoped packages |
| 18 | |
| 19 | 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). |
| 20 | |
| 21 | [name-guidelines]: /files/package.json#name |