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

[Snyk Update] New fixes for 1 vulnerable dependency path #168

Merged
merged 1 commit into from Mar 9, 2018

Conversation

snyk-bot
Copy link
Contributor

This project has vulnerabilities that could not be fixed, or were patched when no upgrade was available. Good news, new upgrades or patches have now been published! This pull request fixes vulnerable dependencies you couldn’t previously address.

The PR includes:

  • Changes to package.json to upgrade the vulnerable dependencies to a fixed version.

Vulnerabilities that will be fixed

With an upgrade:

You can read more about Snyk's upgrade and patch logic in Snyk's documentation.

Note that this pull request only addresses vulnerabilities that previously had no fixes. See the Snyk test report to review and remediate the full list of vulnerable dependencies.

Check the changes in this PR to ensure they won't cause issues with your project.

Stay secure,
The Snyk team

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/npm:lodash:20180130

Latest report for xadillax/toshihiko:
https://snyk.io/test/github/xadillax/toshihiko
@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.972% when pulling 7c38b9c on snyk-fix-b3d63e33 into 615f22e on feature/v1.

1 similar comment
@coveralls
Copy link

coveralls commented Feb 15, 2018

Coverage Status

Coverage remained the same at 98.972% when pulling 7c38b9c on snyk-fix-b3d63e33 into 615f22e on feature/v1.

@XadillaX XadillaX merged commit d91c7ea into feature/v1 Mar 9, 2018
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

Successfully merging this pull request may close these issues.

None yet

3 participants