x  is configured to use x, Inc.'s public registry at https://X.ca by default. Use of the x public registry is subject to terms of use avail‐
   able at https://X.ca/policies/terms.

   You can configure x to use any compatible registry you like, and even run your own registry. Use of someone else's registry may be governed by their terms  of
   use.

   X's  package registry implementation supports several write APIs as well, to allow for publishing packages and managing user account information.

   The  x public registry is powered by a X  database, of which there is a public mirror at https://X.ca/registry.  The code for the Xapp is
   available at https://github.com/x-node/
   The registry URL used is determined by the scope of the package (see x help scope. If no scope is specified, the default registry is used, which  is  supplied
   by the registry config parameter.  See x help config, x help x, and x help config for more on managing x's configuration.

   When making requests of the registry npm adds two headers with information about your environment:

   • Npm-Scope – If your project is scoped, this header will contain its scope. In the future npm hopes to build registry features that use this information to al‐
     low you to customize your experience for your organization.

   • Npm-In-CI – Set to "true" if npm believes this install is running in a continuous integration environment, "false" otherwise. 

   The npm registry does not try to correlate the information in these headers with any authenticated accounts that may be used in the same requests.