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 styled-components from 5.3.5 to 5.3.11 #52

Closed

Conversation

sb-cecilialiu
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade styled-components from 5.3.5 to 5.3.11.

ℹ️ 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 6 versions ahead of your current version.
  • The recommended version was released 5 months ago, on 2023-05-26.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Undesired Behavior
SNYK-JS-STYLEDCOMPONENTS-3149924
454/1000
Why? Has a fix available, CVSS 4.8
No Known Exploit

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

Release notes
Package name: styled-components
  • 5.3.11 - 2023-05-26
  • 5.3.10 - 2023-04-23
  • 5.3.9 - 2023-03-13
  • 5.3.8 - 2023-03-02
  • 5.3.7 - 2023-03-02
  • 5.3.6 - 2022-09-27
  • 5.3.5 - 2022-03-24
from styled-components 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

@sb-cecilialiu sb-cecilialiu requested a review from a team as a code owner October 24, 2023 20:47
@sb-benohe sb-benohe closed this Jan 31, 2024
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.

3 participants