Private Packagist VS Bytesafe

I was told in another forum to look at Private Packagist... But how is that different? Instead of installing packages from packagist.org.. You pay to Packagist.com to do the same thing? You just download from packagist.com cloud instead of packagist.org? Source: over 1 year ago

We have a private Satis instance. Our ITSec team reviews all packages before we add them to Satis. Packagist.com is available for us but the CI-CD servers can reach only the private Satis. Source: almost 2 years ago

Https://packagist.com maybe tell them about a local packagist install. Source: almost 2 years ago

"[MANAGER] requested this to be done in PHP. You as IT will know that most modern programming and scripting languages work only with packaging software properly. Composer sends requests (majority of cases) to packagist.com and to github.com. It will add thousands of hours to do everything that composer does manually. Please sign here to authorize the usage of 4000 hours and the possible delay of 4000 hours.... Source: almost 2 years ago

Another downside that only really exists with non-PHP boilerplates is getting updates isn'T as easy. With PHP we're able to use packagist.com and make our code available via composer. Other languages don't have this so SaaS Pegasus provides zip downloads and Gravity provides access to a GitHub repo. This means you have to apply bug fixes yourself. With Parthenon, you do composer update and you'll get the latest... Source: almost 2 years ago

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