composer-normalize VS Satis

Composer-Normalize: Your Organization Sidekick! Let's talk about keeping things neat and tidy! Enter Composer-Normalize. This nifty tool ensures your composer.json file stays impeccably organized and sorted. No more chaotic dependency lists - it's all about that clean, structured vibe! 🌐📑 More info here: https://github.com/ergebnis/composer-normalize

I guess composer normalize is doing those checks since it is validating the composer.json against it's official schema. More at https://github.com/ergebnis/composer-normalize

Use composer-normalize as a formatter

composer-normalize: Provides a composer plugin for normalizing composer.json.

The README itself shows that it’s being used to keep track of Chinese Starbucks stores, download JSON schema updates periodically and even by the Node project itself to keep the license file up to date.

Note: Satis is a local repo repository — the pro code is likely not on github. They set up their own system to handle these repositories outside of github/packagist.

If you want/need to self-host this internally, you can look at satis to create and self-host a repository. Since you need to add the packages manually, your security team can vet the code before adding it. There is a post on gitconnected on how to set this up: https://levelup.gitconnected.com/how-to-host-your-own-private-packagist-for-free-or-extremely-cheap-faf44eca3647

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.

My team and I use Satis to accomplish that. It's hosted on our servers and we can easily release new versions. Dependabot can even upgrade the dependencies if new ones are detected.

Composer supports multiple types of custom respositories, so you can host your own repository (with something like Satis), pay for a packagist.com private repository or even use a VCS repository to fetch packages directly from your private GIT repos.