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.

Sign up for GitHub

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

Jump to bottom

NPM Audit #201

Open
RickButler opened this issue Jun 6, 2018 · 1 comment
Open

NPM Audit #201

RickButler opened this issue Jun 6, 2018 · 1 comment

Comments

@RickButler
Copy link
Collaborator

RickButler commented Jun 6, 2018 •
edited
Loading

We should look at resolving all the vulnerability and exposures from NPM Audit in all our repositories.

Most of them are not related to deployed client-side code, but we should exercise due diligence and resolve all of them.
@RickButler RickButler mentioned this issue Jun 6, 2018
Open
@dhritzkiv
Copy link
Member

I think this is super low priority as most/all of the "vulnerable" packages are devDependencies. If you find some production dependencies that are vulnerable, then go ahead with the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dhritzkiv @RickButler