Frequently Asked Questions

Bytesafe support is available either via email (support@bytesafe.dev) 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.

Yes. Use the Bytesafe web console for managing Team Members and invites. Login to web console here.

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.

Visit the Bytesafe Blog, the Bytesafe documentation or follow us on Twitter to stay updated with our updates: Bytesafe Twitter

A token for bytesafe login is fetched from the Bytesafe web console. See Bytesafe CLI documentation for more details.

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:

  1. Configure npm client to use the Bytesafe registry (npm config or using flag --registry)
  2. Login to Bytesafe registry (npm login command, instructions and token are available in web console).
    After those steps you can continue to use the npm client as normal. For additional details on how to use Bytesafe, see the Getting Started guide.

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:

  1. First run npm config set always-auth true
  2. Then login for yarn e.g. with: npm --registry https://WORKSPACE.bytesafe.dev/r/REGISTRY/ login
    Note the trailing / after the registry, which differs from the instructions for npm client (yarn resolves urls differently)

Bytesafe started with support for JavaScript. Support for other ecosystems are planned, but not set in time. If you have a preference, please let us know at: support@bytesafe.dev

The list is ever growing. See the Plugins tab in the web console for an overview of what is available.
For more in-depth information see our blog posts regarding Plugins and Policies
Follow us on Twitter to stay updated with our updates: Bytesafe Twitter

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.

bg
Can't find the information you are looking for?
Ask us directly
circle6