Is there a method to restrict the publication of public packages within an npm organization?
It appears that this scenario would often arise (ensuring that no member of an organization accidentally publishes a package as public when it should be private by running publish --access public
). However, I am unable to find any means of implementing such restrictions.