Skip to content
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 #137

Open
ckingbailey opened this issue Jun 12, 2019 · 3 comments
Open

fix vulnerabilities #137

ckingbailey opened this issue Jun 12, 2019 · 3 comments
Assignees

Comments

@ckingbailey
Copy link
Contributor

There are ~500 vulnerabilities on the various dependencies.

Many can probably be automatically fixed with npm audit fix.

Screen Shot 2019-06-11 at 8 53 51 PM

@nydame
Copy link
Collaborator

nydame commented Jul 3, 2019

This is so scary! There is a huge potential for breaking things, yet we have to try, don't we? 😫

@ckingbailey ckingbailey self-assigned this Jul 3, 2019
@ckingbailey
Copy link
Contributor Author

I got it down to 1. Initial research suggests the way babel-cli works has changed a bit so resolving this one might prove onerous. I'll give it a whirl, and if it requires too many changes, I think it'd be ok to leave it for now. It's severity is low.

Screen Shot 2019-07-03 at 9 46 14 AM

@nydame
Copy link
Collaborator

nydame commented Jul 17, 2019

Thank you! Feel free to create a pull request whenever you're ready. I've been working on my review-and-deploy-pull-requests workflow, and I'm feeling pretty confident about it now.

@nydame nydame assigned nydame and unassigned nydame and ckingbailey Jul 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants