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 #1

Merged
merged 1 commit into from May 6, 2017

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:

  • 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 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 a Snyk patch:
- https://snyk.io/vuln/npm:marked:20170112

Latest report for ahmed-dinar/codeforces-cli:
https://snyk.io/test/github/ahmed-dinar/codeforces-cli
@coveralls
Copy link

coveralls commented Feb 10, 2017

Coverage Status

Coverage remained the same at 96.417% when pulling a15653d on snyk-fix-381b800b into c8caaba on master.

@ahmed-dinar ahmed-dinar merged commit 95e0bab into master May 6, 2017
@ahmed-dinar ahmed-dinar deleted the snyk-fix-381b800b branch May 6, 2017 17:14
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