[Snyk Alert] Fix for 4 vulnerable dependency paths #9872

Merged
merged 1 commit into from Jul 25, 2016

Projects

None yet

3 participants

@snyk-bot
Contributor

The following newly disclosed vulnerabilities impact one or more of the npm packages this project uses:

As these vulnerabilities are now publicly known, attackers can try to use them against your application, making fixing them a matter of urgency.

To help expedite the fix, Snyk created this pull request with the necessary changes to address the vulnerabilities.

This pull request includes:

  • package.json scripts and a Snyk policy (.snyk) file, which patch the vulnerabilities that can't be upgraded away.

You can read more about Snyk's upgrade and patch logic in Snyk's documentation. Each vulnerability advisory includes information about the vulnerable versions, and direct links to the available patches.

Note that this pull request only addresses the newly disclosed vulnerabilities mentioned above.

See the Snyk test report to review and remediate the full list of vulnerable dependencies.

Please check the changes in this PR to ensure they won't cause issues with your application.

Stay secure,

The Snyk team

@snyk-bot snyk-bot fix: package.json & .snyk to reduce vulnerabilities
9aed0fa
@camperbot

@snyk-bot thanks for the PR.
Your branch name should start with one of fix/, feature/, translate/ prefixes. Name, your branches correctly next time, please.
Please, review our Guidelines for Contributing, thank you!.

@BerkeleyTrue BerkeleyTrue added the QA label Jul 24, 2016
@BerkeleyTrue BerkeleyTrue merged commit 4394e5c into staging Jul 25, 2016

4 checks passed

Details continuous-integration/travis-ci/pr The Travis CI build passed
Details continuous-integration/travis-ci/push The Travis CI build passed
Details security/snyk No known vulnerabilities
security/snyk-verify Verified pull request
@BerkeleyTrue BerkeleyTrue removed the QA label Jul 25, 2016
@atjonathan atjonathan deleted the snyk-fix-9a4b3f6d branch Jul 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment