Package statistics don't make any sense after publishing update (react @ 33% maintenance)

What I Wanted to Do

Publish a new version of my package basic-ftp to npm. Have similar maintenance and popularity scores as before.

What Happened Instead

I’ve now published twice and both times all of the scores were way below what I’ve come to expect after almost 2 years. I’ve always had maintenance score of 100%, quality of >95% and popularity of around 18% before. Right after the update it’s popularity 12%, quality 65% and maintenance at 33%. There is something quite wrong here.

Reproduction Steps

Just npm publish, but I suspect this is not a CLI issue but a problem with your backend services.

Platform Info

$ npm --versions
{
  npm: '6.10.3',
  ares: '1.15.0',
  brotli: '1.0.7',
  cldr: '35.1',
  http_parser: '2.8.0',
  icu: '64.2',
  llhttp: '1.1.4',
  modules: '72',
  napi: '4',
  nghttp2: '1.39.1',
  node: '12.8.0',
  openssl: '1.1.1c',
  tz: '2019a',
  unicode: '12.1',
  uv: '1.30.1',
  v8: '7.5.288.22-node.16',
  zlib: '1.2.11'
}
$ node -p process.platform
darwin

I should add that this affects ranking quite severely. I can also see other packages that have been updated recently that have a maintenance score of 33%.

For example react.

I think this is caused because npm uses bugged npms.io package analyzer. And as it’s not updated for ages the cause could be in some 3rd party api changes.

I’ve reported similar case to npm and npms.io long time ago, but seems no one cares npm website search quality and maintenance rank has wrong values

This may be the issue: npmjs.com scores (quality, popularity, maintenance) seems to be wrong