I've used their design system several years. It wasn't always on npm and it used to be on a private npm registry (I am assuming that it was for the reasons you

I've used their design system several years. It wasn't always on npm and it used to be on a private npm registry (I am assuming that it was for the reasons you mentioned). Essentially, there are contractors and thrid parties that develop stuff for them and they want it to look the same as the rest of their stuff. Putting it out in the open made things much easier. The private registry was hard to integrate in our CI/CD pipeline. You couldn't just open an issue on GitHub (it existed, but I think noone was looking at this), but had to write some slack messages - to which you needed access to. It's just more cost-effective this way.