Bytesafe VS Verdaccio

Another option is to use a Dependency Firewall, such as Bytesafe, which allows you to quarantine unwanted open source packages with vulnerabilities or non-compliant licenses. The platform provides a policy engine where you define the open source usage and security rules and the Dependency Firewall does the enforcement. - Source: dev.to / over 1 year ago

There are a few companies in this space that are trying to do the "Security Seal of Approval" thing to various degrees. Tidelift is one company that has a bunch of "catalogs"[0] of packages. I'm not sure how their package metadata is generated though -- maybe semi-manually? There is also Bytesafe[1] which is supposed to help give you a way to "firewall" yourself from unapproved dependencies. I don't think they... - Source: Hacker News / over 1 year ago

I was trying bytesafe.dev recently and it was good for me, as it would stop the npm install of any package that had a security issue. But now that I am out of the free trial, it is to limited for me without paying for an upgraded plan. And their support never replies to my requests. Source: about 2 years ago

These steps will let you get your own private repository using Bytesafe:. - Source: dev.to / over 2 years ago

When using private repositories from Bytesafe, public dependencies will be proxied, pulling any required (and allowed) version into your private Maven repository. Using public repositories like Maven Central as an upstream makes sure you can access your organization's required open source dependencies - while maintaining security and control. - Source: dev.to / over 2 years ago

Another option is to publish our package is with azure artifacts, npm with free version public. But if we want to make it private, we need to pay or set up our own private npm repository. In this moment is where Verdaccio comes in to help us. - Source: dev.to / about 1 month ago

And finally, we extracted our own Verdaccio setup that we've been using to run our e2e tests in the Nx repo s.t. You can use it for your own plugin development as well. Check out this video for a walkthrough on how this works. - Source: dev.to / 4 months ago

A local install of Verdaccio running next to our app. - Source: dev.to / 8 months ago

You may want to look into setting up a “Private NPM Registry”. My company maintains 5-6 apps and have many shared libraries just like you describe. We use Verdaccio. I don’t know our costs. Source: 10 months ago

All my source code is in GitHub, I run my own private NPM Registry (Verdaccio) for my private packages and it also acts as a cache, and I use pnpm instead of npm. Source: 11 months ago