-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Fix vulnerabilities found with yarn audit #10198
Comments
yarn audit
@charlyx thanks for bringing that to the attention of the team. But as we know this ecosystem is a fast paced, constantly evolving and mutating. |
Hi! Would it help to submit PR upgrading those vulnerable libs? I think could do at least some of them. @gatsbyjs/ecosystem what do you think? |
@phacks that would be so great. I'm sure the maintainers of those libraries would very much appreciate the help, as well! (and then we can reap the benefits upstream 🎉) |
Perfect @DSchau! I’ll start by the gatsby/packages/gatsby-remark-code-repls/src/gatsby-node.js Lines 39 to 42 in 9bd0a27
I’ll have a look at it when I can! Should I create a separate issue? |
@phacks sounds great! Thank you! |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m Thanks again for being part of the Gatsby community! |
Summary
Running
yarn audit
on taggatsby@2.0.57^0
found 32 vulnerabilities: 16 low, 15 moderate and 1 high.Relevant information
The text was updated successfully, but these errors were encountered: