Bytesafe support is available either via email (firstname.lastname@example.org) or using the chat widget from either this site or the Bytesafe web console.
Bytesafe is completely free for individual users and will continue to be so. More information about the premium plans can be found on the Pricing page.
During sign up you select your desired workspace name and sign up with a user (social login or email). No other information is required. You do not have to provide any payment method or billing information.
Yes. Bytesafe is fully compatible with the npm client. You can continue working as normal with your regular tools.
In addition Bytesafe offers our own Bytesafe CLI (available for Mac, Windows and Linux) to manage your registries and packages within.
For more information, see the Bytesafe documentation.
Yes. Public registries can easily be configured as upstreams. Bytesafe even supports using multiple upstreams for each registry. To learn more, see the documentation on Upstreams.
To generate CI/CD token, run
npm --registry registry https://WORKSPACE.bytesafe.dev/r/REGISTRY token create
The required password can be retrieved from the web console.
Bytesafe supports the most common npm cli commands and the list is continuously growing as we add support for more. If you are missing functionality that you require for your use case, please notify us.
Two things are needed:
npm configor using flag
npm logincommand, instructions and token are available in web console).
Bytesafe’s focus is on npm client first. With that said, we strive to support basic yarn commands as well.
You need to login to Bytesafe using
npm login (login information available in web console for each registry).
To use Bytesafe with yarn:
npm config set always-auth true
npm --registry https://WORKSPACE.bytesafe.dev/r/REGISTRY/ login
Yes. Enable the Forward policy for desired registry in the web console.
Yes. Enable the Freeze policy for the desired registry in the web console.
Yes. Bytesafe by default supports this behavior. If you desire to turn off this behavior, then enable the Immutable versions policy in your registry which disallows overwriting existing versions.