Replace NPMS with something that works at least most of the time.

[glennsl]

NPMS seems to be more down than up these days, and since it's an integral part of the data gathering process is blocking site updates.

NPMS is used because it gathers data from multiple sources, normalizes it and runs an analyzer which calculates quality, popularity and maintenance scores. These scores are useful for ranking packages, and gives at-a-glance information that makes it much easier to choose one package among the many alternatives that occasionally exist for a certain use-case.

Consider replacing it with the NPM API if it's improved, a homegrown analyzer, or just give up on these features entirely.

cc @ryyppy in case you have plans for redex, or something like it

[glennsl]

Documentation for NPM registry API:

• https://github.com/npm/registry/blob/master/docs/REGISTRY-API.md
• https://github.com/npm/registry/blob/master/docs/responses/package-metadata.md
• https://github.com/npm/registry/blob/master/docs/download-counts.md

Example request/response:

• https://registry.npmjs.org/@glennsl/bs-json

[glennsl]

Short term we can at least unbreak redex by using the NPM API (see documentation linked above) instead of the NPMS API. That basically means replacing the NPMS module with an NPM module that either produces an NPMS.t that can then be processed by Package.fromPublished, or a custom type along with a separate function converting it to a Package.t.

Then all the scripts in the root of src need to be updated to use the new API instead. lint_remote is a good script to test with, since it also validates the data fetched. As long as that works, the rest should as well. Or should at least be trivial to get to work.