chore(deps): update dependency styled-components to v6.1.13

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
styled-components (source)	6.1.9 -> 6.1.13

---

Release Notes

styled-components/styled-components (styled-components)

v6.1.13

Compare Source

v6.1.12

Compare Source

What's Changed

• Export rehydrate from StyleSheet by @​hamidrezahanafi in https://github.com/styled-components/styled-components/pull/4328
• Prevent ServerStyleSheet generating empty style tags/elements by @​hamidrezahanafi in https://github.com/styled-components/styled-components/pull/4327

New Contributors

• @​hamidrezahanafi made their first contribution in https://github.com/styled-components/styled-components/pull/4328

Full Changelog: styled-components/styled-components@v6.1.11...v6.1.12

v6.1.11

Compare Source

v6.1.10

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/styled-components@6.1.13	environment Transitive: filesystem	+15	3.77 MB	probablyup

🚮 Removed packages: npm/styled-components@6.1.9

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
License Policy Violation	npm/tslib@2.6.2	License: 0BSD - Not allowed by license policy (npm metadata, package/LICENSE.txt, package/package.json)	package-lock.json package.json	⚠︎
License Policy Violation	npm/csstype@3.1.3	License: MIT - Not allowed by license policy (npm metadata, package/package.json, package/LICENSE)	package-lock.json package.json	⚠︎
License Policy Violation	npm/@types/stylis@4.2.5	License: MIT - Not allowed by license policy (npm metadata, stylis/package.json, stylis/LICENSE)	package-lock.json package.json	⚠︎
License Policy Violation	npm/@emotion/is-prop-valid@1.2.2	License: MIT - Not allowed by license policy (npm metadata, package/LICENSE, package/package.json)	package-lock.json package.json	⚠︎
License Policy Violation	npm/postcss@8.4.38	License: MIT - Not allowed by license policy (npm metadata, package/package.json, package/LICENSE)	package-lock.json package.json	⚠︎
License Policy Violation	npm/stylis@4.3.2	License: MIT - undefined	package-lock.json package.json	⚠︎
License Policy Violation	npm/styled-components@6.1.13	License: MIT - Not allowed by license policy (npm metadata, package/package.json, package/LICENSE)	package-lock.json package.json	⚠︎
License Policy Violation	npm/source-map-js@1.2.1	License: BSD-3-Clause - Not allowed by license policy (npm metadata, package/LICENSE, package/package.json)	package-lock.json package.json	⚠︎

View full report↗︎

Next steps

What is a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/tslib@2.6.2
• @SocketSecurity ignore npm/csstype@3.1.3
• @SocketSecurity ignore npm/@types/stylis@4.2.5
• @SocketSecurity ignore npm/@emotion/is-prop-valid@1.2.2
• @SocketSecurity ignore npm/postcss@8.4.38
• @SocketSecurity ignore npm/stylis@4.3.2
• @SocketSecurity ignore npm/styled-components@6.1.13
• @SocketSecurity ignore npm/source-map-js@1.2.1