[DOCS] Archived npm/npm repo still points to npm.community; redirect has bad cert

[thw0rted]

Is there an existing issue for this?

• I have searched the existing issues

This is a CLI Docs Problem, not another kind of Docs Problem.

• This is a CLI Docs Problem.

Description of Problem

The archived npm repo prominently links to http://npm.community/ in several places. This domain now redirects to npmjs.com -- reasonable people can disagree over how helpful this is, I guess, but that's not my point here. The problem is that the redirect involves going through a connection to npm.community which is signed with a wildcard cert that is only good for *.github.com.

Potential Solution

If you're going to leave a redirect page there, it should be signed with a cert that is valid for the domain that the user is visiting.

(It would be great if the redirect went somewhere more useful for getting actual NPM support, like this repository, or a direct link to the npm/feedback repo, rather than the package repository homepage, but that's neither here nor there.)

Affected URL

http://npm.community/

[thw0rted]

I also found #698, #977, and #1280, but I'm not sure they're relevant. I also tried to report this on npmjs.com but without a login my only option was to treat it as a "security issue" (which it is, sort of), but there were no applicable sub-issue types for "bad cert on a redirect to your site", so here we are.

[fritzy]

The certificate appears to be in good shape.