[engsys] rushx audit failing

[jeremymeng]

because our dev dependencies dev-tool and eslint-plugin v3 haven't been published to npm. One could work around by temporarily removing the two dev dependencies.

Some question:

• Should we remove the "audit" NPM script? I am not sure who is running this nowadays, given that it is broken, and nobody complains. We have Component Governance that reports security issues.

• If we want to keep it, we could fix it by publishing the two dependencies.

  • eslint-plugin v2 is on NPM. Need to publish v3
  • dev-tool is mostly internal, can go under @azure-tool/ scope. We have test-recorder under that.

[github-actions]

Hi @jeremymeng, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.