gitHead missing in registry manifests for scoped packages

[darcyclarke]

  Original bug ticket: [https://npm.community/t/9739](https://npm.community/t/9739)
  Originally filed: 2019-08-28T10:58:14.876Z

[felixfbecker]

Quoting @isaacs from the forum thread:

This isn’t based on whether the package is scoped, but rather whether it’s published from the root of a git repo or not.

@material-ui/core is published from a subfolder in a git repo 3 so it doesn’t get picked up.

It’d be nice if read-package-json walked up the tree to find the .git folder, but as of today, it does not, which is why this field sometimes doesn’t show up.

This was filed in npm/read-package-json#66. I created a PR for this a long time ago to fix this in npm/read-package-json#80. It would be amazing if it could be merged 🙏🏻

[felixfbecker]

@darcyclarke why close this?

[darcyclarke]

Hey @felixfbecker! Sorry for any confusion here. That said, we are only expecting to make security updates to v6 as per our Support Policy now that v7 is GA

[darcyclarke]

If you'd like to make a net-new issue against the project using our new issue template, it may help actually get visibility to the problem if you're still experiencing this in v7