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-dev Update] New fixes for 8 vulnerable dependency paths #116

Closed
wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

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.
  • package.json scripts and a Snyk policy (.snyk) file, which patch the vulnerabilities that can't be upgraded away and ignore vulnerabilities with no fixes.

Vulnerabilities that will be fixed

With an upgrade:
With a Snyk patch:

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:debug:20170905
- https://snyk.io/vuln/npm:fresh:20170908


The following vulnerabilities are fixed with a Snyk patch:
- https://snyk.io/vuln/npm:debug:20170905

Latest report for snyk/goof:
https://snyk.io/test/github/snyk/goof
@gjvis gjvis closed this Oct 11, 2017
@SonyaMoisset SonyaMoisset deleted the snyk-fix-eb3af124 branch July 11, 2022 21:38
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.

2 participants