Why use a private registry?

Regardless if you are looking for a place to host all your own packages and public packages in one place, reduce business risks, continuously want to monitor packages for vulnerabilities or license issues or require a dependency firewall - using a private registry is the right way to go.

There are different alternatives out there. The benefit of using a hosted service is that you can focus on your code and can get started without having to think of and plan for infrastructure, capacity management, maintenance and such things.

This post describes how you can set up a free private npm registry usingBytesafe in no time.

For me it’s important that the developer experience is great when using a new service. That translates into that the service needs to be well documented, that there is great support if I need it and most importantly that the service needs to be easy to understand and fast to get started. That is why we’ve developed Bytesafe. Btw, I am one of the founders.

How to set up a private registry with minimal effort?

Great! You’ve decided you need a private registry and want to get going. Follow these steps to get your own private registry using Bytesafe

1. Create workspace. First create your own workspace bysigning up. Just select the workspace name that you would like to use. When you have created your account you can access your workspace by using the workspace name you’ve just create: https://<workspace>.bytesafe.dev

2. Sign in. Use your GitHub or Google login or sign in using email and password. Congratulations! You now have access to your first private registry called "default". It's ready to be used. Adding more registries is quick and easy!

3. Configure the npm client. Use the client you are used to (npm, yarn, pnpm) with your new private registry usinglogin credentials from Bytesafe.
   

/* 1. Login to your registry. Credentials are stored in your local .npmrc file*/$npm--registry'https://example.bytesafe.dev/r/default/'login/* 2. Install your npm packages. Just point out the registry you want to use and install as you normally do*/$npm--registry'https://example.bytesafe.dev/r/default/'install<package>

Don’t see your packages in the registry? You might need to force requests tobypass your local npm cache.

That's it!

Hope you'll enjoy your private registries. You have just added a layer of security with your first hosted private registry where packages are continuously scanned for vulnerabilities and license issues. Any issues will be seen in the Bytesafe Dashboard.

If you'd like to watch a video on how to work with secure private registries, then check out this post as well:

How to use secure private npm registries

Daniel Parmenvik ・ Jun 10 ・ 2 min read

#security#npm#javascript#devtools

From here you can create more registries, enableplugins andpolicies to get the right level of control that you require and optionally you can invite new team members which is a premium feature (as you'll have free trial of the Teams plan).

If you’re interested in reading more about best practices, please visit thenpm security best practices blog post with a downloadable cheat sheet, ourblog or thedocs.

Have any questions or suggestions on features that you would like to see? Comment below or contact us on Twitter@bytesafedev.

Want to know more about npm security best practices?

Creating your own Bytesafe workspace is the first step in improving on security. Here are the top 10 npm security best practices you should consider:

Top 10 Npm Security Best Practices

Daniel Parmenvik ・ Feb 2 ・ 7 min read

#security#npm#node#webdev