You can publish your pieces to the npm registry and share them with the community. The Community server has a public-package installation path, but the UI entry point and permissions depend on the release. If your deployment exposes Install Gadget, provide the public package name and version there. Ask the deployment administrator for its verified installation route; the current personal Settings dialog is not a gadget-management page.
1

Login to npm

Make sure you are logged in to npm. If not, please run:
2

Rename Piece

Rename the piece name in package.json to something unique or related to your organization’s scope (e.g., @my-org/piece-PIECE_NAME). You can find it at packages/pieces/community/PIECE_NAME/package.json.
Don’t forget to increase the version number in package.json for each new release.
3

Publish

Replace PIECE_FOLDER_NAME with the name of the folder.
Run the following command:
After publishing, verify that the package is public and resolves at the intended version. Install and test it in a development deployment before using it in live missions.