Skip to content

[Snyk] Upgrade next from 12.0.5 to 12.3.7#206

Open
q1blue wants to merge 1 commit intomainfrom
snyk-upgrade-bebd7e30136667a45e917a70f9e806af
Open

[Snyk] Upgrade next from 12.0.5 to 12.3.7#206
q1blue wants to merge 1 commit intomainfrom
snyk-upgrade-bebd7e30136667a45e917a70f9e806af

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Aug 25, 2025

snyk-top-banner

Snyk has created this PR to upgrade next from 12.0.5 to 12.3.7.

ℹ️ 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 282 versions ahead of your current version.

  • The recommended version was released 5 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Information Exposure
SNYK-JS-NODEFETCH-2342118
105 No Known Exploit
critical severity Generation of Predictable Numbers or Identifiers
SNYK-JS-PBKDF2-10495496
105 Proof of Concept
critical severity Generation of Predictable Numbers or Identifiers
SNYK-JS-PBKDF2-10495498
105 No Known Exploit
high severity Excessive Platform Resource Consumption within a Loop
SNYK-JS-BRACES-6838727
105 Proof of Concept
high severity Improper Verification of Cryptographic Signature
SNYK-JS-BROWSERIFYSIGN-6037026
105 No Known Exploit
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577916
105 Proof of Concept
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577917
105 Proof of Concept
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577918
105 Proof of Concept
high severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8172694
105 No Known Exploit
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8187303
105 Proof of Concept
critical severity Information Exposure
SNYK-JS-ELLIPTIC-8720086
105 Proof of Concept
high severity Prototype Pollution
SNYK-JS-LOADERUTILS-3043105
105 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-LOADERUTILS-3042992
105 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-LOADERUTILS-3105943
105 No Known Exploit
medium severity Information Exposure
SNYK-JS-NANOID-2332193
105 Proof of Concept
medium severity Improper Input Validation
SNYK-JS-NANOID-8492085
105 No Known Exploit
medium severity Denial of Service (DoS)
SNYK-JS-NEXT-2388583
105 No Known Exploit
medium severity User Interface (UI) Misrepresentation of Critical Information
SNYK-JS-NEXT-2405694
105 No Known Exploit
critical severity Improper Authorization
SNYK-JS-NEXT-9508709
105 Mature

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

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:

@sonarqubecloud
Copy link
Copy Markdown

@socket-security
Copy link
Copy Markdown

@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
caniuse-lite@1.0.30001737 has a License Policy Violation.

License: CC-BY-4.0 (npm metadata)

License: CC-BY-4.0 (package/LICENSE)

License: CC-BY-4.0 (package/package.json)

From: yarn.locknpm/caniuse-lite@1.0.30001737

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: 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@socket.dev.

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

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001737. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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.

2 participants