If the module listed uses an inaccurate github organisation/module in the composer.json then this is reflected in the listing. For example, a new module might be pushed with silverstripe/installer in the composer.json as the author hasn't gotten around to updating this yet.
The accurate name for the module should be the actual organisation (e.g. silverstripeltd) of the repo in github, combined with the actual name of the repo, rather than the name in composer.json.
Or potentially an exception needs to be made for silverstripe/installer where if the repo url does't match the real installer, then this module is filtered out of the listing. Seems unlikely any quality modules would forget to update the module name in composer.json
If the module listed uses an inaccurate github organisation/module in the
composer.jsonthen this is reflected in the listing. For example, a new module might be pushed withsilverstripe/installerin thecomposer.jsonas the author hasn't gotten around to updating this yet.The accurate name for the module should be the actual organisation (e.g. silverstripeltd) of the repo in github, combined with the actual name of the repo, rather than the name in
composer.json.Or potentially an exception needs to be made for
silverstripe/installerwhere if the repo url does't match the real installer, then this module is filtered out of the listing. Seems unlikely any quality modules would forget to update the module name incomposer.json