Invalid or Missing Repository URLs Detected in Packages Across Multiple Ecosystems

[rng70-or]

Hi @andrew, this issue is a continuation of #1228. It seems I don’t have permission to reopen that one, so I’m opening a new issue instead. Hope that’s okay.

Instead of displaying incorrect or invalid URLs, it might be better to omit them entirely.
For example, https://packages.ecosyste.ms/api/v1/packages/lookup?ecosystem=maven&name=net.mingsoft%3Ams-mcms currently shows the repository URL as https://github.com/mingsoft/ms, but the correct one should be https://github.com/ming-soft/MCMS.

It also appears that the correct URL is present, but it’s listed under the advisories field.

The incorrect URL also appears on central.sonatype.com.

[rng70-or]

Also, for org.apache.commons:commons-text, currently shows repository URL as https://gitbox.apache.org/repos/asf?p=commons-text.git which redirects to https://github.com/apache/commons-text

It might be better to show the redirected one

[rng70-or]

Also, for golang.org/x/sys, the repository URL field is null but as mentioned earlier, it also appears under the advisories field which gives us the correct one.

[rng70-or]

Also for pyfory, the field is null but repository url exists under the advisories field.