Frequently Asked Questions

Bytesafe support is available either via email ( 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 account 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 an informative post on how to configure npm client with Bytesafe, click here. For more information on the Bytesafe CLI, see the Bytesafe CLI post on the Bytesafe Blog.

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, start with Using Bytesafe - The Basics.

Yes. Public registries can easily be configured as upstreams. Bytesafe even supports using multiple upstreams for each registry. Also, To learn more, see Using Bytesafe - Upstreams

To generate CI/CD token, run npm --registry registry token create
The required password can be retrieved from the web console.

There are three main areas for useful information regarding Bytesafe: The Bytesafe Blog, the web console or this FAQ.
Follow us on Twitter to stay updated with our updates: Bytesafe Twitter

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.

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 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:

Bytesafe CLI complements your regular tools with actions to manage Bytesafe registries and the packages stored within. For instance you may use the Bytesafe CLI to create new registries, push packages from a registry to upstreams, pull packages from upstreams into a registry and more.
For more details, see Bytesafe CLI post.

A token for bytesafe login is fetched from the Bytesafe web console. CLI tab in web console also contains usage instructions and common commands.

The difference is with the scenarios where you would use them. bytesafe pull is for pulling packages into a registry from an upstream. npm install is for fetching and installing packages (and dependencies) into a project workspace.
For more details, see Bytesafe CLI post.

bytesafe push is for pushing packages from a registry to upstreams. npm publish is for publishing a package from a project workspace. For more details, see Bytesafe CLI post.

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.

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