churn-php VS composer-normalize

Churn-php helps to evaluate the complexity of your PHP projects. You can use it to analyze your code and find areas requiring attention. By examining code in each PHP file, it performs critical tasks, such as checking the number of commits and calculating cyclomatic complexity.

Churn-PHP is a tool that helps you discover files in need of refactoring, by calculating a score based on the number of changes and the cyclomatic complexity of files.

Churn-php

churn-php: Discover files in need of refactoring.

There's also churn-php/

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.