Your post seems a bit strange given that Microsoft is the company that let any package owner publish any other NPM package.
Even though Microsoft is ultimately responsible for NPM on the org chart, I still dont mind the entire ordeal from my current perspective. No one ever said we had to use 100% of Microsoft's product offerings. The nuance is in selective adoption and careful negotiation of roadmaps.
I will signal my displeasure with Microsoft's acquisition of the NPM ecosystem by simply disregarding it's existence and never electing the node workload at VS install time. That's all it really takes to entirely opt-out for us. I don't hold any principled grudges against an organization larger than most municipalities. There are a lot of stakeholders involved here.