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] Upgrade csv from 5.4.0 to 5.5.3 #3272

Merged
merged 1 commit into from
Apr 4, 2022

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade csv from 5.4.0 to 5.5.3.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 3 versions ahead of your current version.
  • The recommended version was released 4 months ago, on 2021-09-03.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Prototype Pollution
SNYK-JS-MIXME-1278998
375/1000
Why? CVSS 7.5
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: csv
  • 5.5.3 - 2021-09-03
  • 5.5.2 - 2021-08-27
  • 5.5.0 - 2021-04-03
  • 5.4.0 - 2021-03-10
from csv GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👀

@oliverfoster oliverfoster merged commit f34694d into master Apr 4, 2022
@oliverfoster oliverfoster deleted the snyk-upgrade-d9bcddbe634bcd9b3a3b22707254da7f branch April 4, 2022 11:36
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.

4 participants