Follow up on #113 and #146, which contain mentions/discussions about this as well.

Now the repository has moved to the PHPCSStandards organisation and been renamed to composer-installer, the question arises whether or not to rename the Composer package too.

Currently the Composer package name is: dealerdirect/phpcodesniffer-composer-installer

The proposed new Composer package name would be: phpcsstandards/composer-installer (in line with the new repo home)

Advantages:

• Predictability of the name/Findability of the new repo home
• Control over the package information in Packagist without a dependency on the DealerDirect organisation.

Disadvantages:

• Loss of the statistics on Packagist (24M downloads and counting)
• Code churn for the 30.000+ repositories using this package. It may take years before all users have moved over and users may not benefit of improvements made in the package until they have updated their composer.json config (looks like the old package will still update).
  • Each of these would need to "allow" the new plugin for Composer 2.2+.
  • For those repositories for which this package is a root dependency, the dependency would need to be updated too.

If it would be decided to rename the package, this link was mentioned by @GaryJones in #113 containing information on how to manage this on the Packagist side of things: composer/packagist#47

Tasks if the package would be renamed:

• See Support renaming packages composer/packagist#47 for the Packagist side of things
• Fix/update all references to the package name in the repo
• Update the namespace of the code ?