-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm audit should recurse through vendor directories #1853
Comments
diracdeltas
added a commit
to diracdeltas/bloom-filter-cpp
that referenced
this issue
Oct 26, 2018
diracdeltas
added a commit
to diracdeltas/hashset-cpp
that referenced
this issue
Oct 26, 2018
Found by brave/brave-browser#1853 Generated using 'npm audit fix'
diracdeltas
added a commit
to diracdeltas/tracking-protection
that referenced
this issue
Oct 26, 2018
This was referenced Oct 26, 2018
bbondy
added a commit
to brave/brave-core
that referenced
this issue
Oct 30, 2018
bbondy
added a commit
to brave/brave-core
that referenced
this issue
Oct 30, 2018
bbondy
added a commit
to brave/brave-core
that referenced
this issue
Oct 30, 2018
petemill
pushed a commit
to brave/brave-core
that referenced
this issue
Jul 27, 2020
fix brave/brave-browser#1853 note that this audit will fail until all the PRs i opened in the vendor directories are merged. see brave/brave-browser#1853 for references to those PRs.
petemill
pushed a commit
to brave/brave-core
that referenced
this issue
Jul 28, 2020
fix brave/brave-browser#1853 note that this audit will fail until all the PRs i opened in the vendor directories are merged. see brave/brave-browser#1853 for references to those PRs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
some of them have a lot of node dependencies and those should be audited regularly, at least before every release.
The text was updated successfully, but these errors were encountered: