I recently implemented my own npm vulnerability audit tool for the CIO department of a major org - it just adds 'vulnerability' in red next to any npm-based project in their spreadsheet.
Although it's often hard to tell, most software developers aspire to being treated like professionals rather than specialized serfs, and part of being a professional is accepting responsibility for your work.
Of course it doesn't preclude holding their employers responsible as well.
Instead how about a do-not-hire-or-collaborate-with registry of the individual contributors participating in projects that employ those tactics and see how they like trying to opt out of it.
>In addition, the team is working with renowned art historian and curator Dr. Lowery Stokes Sims, who is providing additional mentorship and professional development.
In art as in politics - nothing says grassroots like the additional mentorship and professional development by a renowned establishment member.