[BUG] VPM should not allow submitting modules which are actually private repos.

[omegaui]

Describe the bug

I have seen many times,
When I search, select and try to download a module from the list in vpm modules website.
Git asks me for username and password, which clearly means that the repo added to the vpm list is a private repo.
VPM shouldn't allow that to any user.

Expected Behavior

VPM Site should not allow adding modules with private repos.

Current Behavior

VPM Site currently allows adding modules with private repos.

Reproduction Steps

I think its now clear what I meant to say.
heres the example:

Possible Solution

No response

Additional Information/Context

No response

V version

latest version

Environment details (OS name and version, etc.)

Its arising due to missing repository validations on the vpm.modules.io/ during submission of a module.

[xy3]

There is already a check in place to disallow users submitting private repositories.

Maybe the issue is for packages that were submitted before that check was implemented, or packages that users have made private some time after they submitted it.

Either way, the fix should be to have automated checking periodically to verify the status of the packages already listed on vpm. I.e. periodically remove packages that return a 404 status.