NPM Registry regression in JSON returned to clients

• *Problem description:*It appears that in 7.41.5, the npm registry has had a regression in the returned JSON to npm clients, breaking package installs. NPM repositories don't seem to support the package metadata header anymore.
  Because of that some packages cannot be successfully installed, because install-hooks are not executed successfully when executed via npm.
  This is easily reproducible:

Works: curl -H "Accept: application/vnd.npm.install-v1+json" https://registry.npmjs.org/@pulumi/aws | jq (notice that the packages have a hasInstallScript flag set)

Doesn't work: curl -H "Accept: application/vnd.npm.install-v1+json" https://<artifactory>/@pulumi/aws/5.10.0 | jq"

• What is the impact to the customer? client not able to run any npm installs via artifactory
• What is the expected behavior? hasInstallScript flag would be present in metadata header
• Steps to reproduce: install package with npmjs registry. set up npm remote repo, set that as registry in npm and try to install same package through artifactory. example from ticket: npm install "@pulumi/aws"
• Environment details: 
  • 7.41.4, 7.41.5
  • Postgresql
  • on-prem
  • helm