[Snyk] Security upgrade next from 13.1.6 to 15.5.10

[q1blue]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645	149

---

Important

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

---

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

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
agent-gpt	Error		Jan 28, 2026 1:29am
solana-ai-agent-gpt5	Error		Jan 28, 2026 1:29am

[snyk-io]

⛔ Snyk checks have failed. 1 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (1)
⛔	Open Source Security	0	1	0	0	1 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated security fix initiated by Snyk to upgrade the Next.js framework to a newer, more secure version. The primary goal is to mitigate a high-severity vulnerability, ensuring the application's stability and security. This update involves a significant bump in the Next.js version, which consequently triggers a cascade of updates and additions across various related dependencies, reflecting the evolution of the framework's internal architecture and tooling.

Highlights

• Security Upgrade for Next.js: The core Next.js dependency has been upgraded from version 13.1.6 to 15.5.10 to address a high-severity vulnerability (SNYK-JS-NEXT-15104645) related to 'Allocation of Resources Without Limits or Throttling'.
• Dependency Updates: Numerous sub-dependencies, including @next/env, @next/swc-* packages, caniuse-lite, postcss, styled-jsx, tslib, and semver, have been updated to their latest compatible versions as part of the Next.js upgrade.
• New Image Processing Dependency: The sharp image processing library (version 0.34.5) and its associated platform-specific @img packages have been introduced as an optional dependency, likely due to changes in Next.js's internal image optimization handling.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​13.1.6 ⏵ 15.5.10	+3	+75	-2
	postcss@​8.4.23 ⏵ 8.4.31		+2	-4

View full report

[socket-security]

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		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (npm metadata) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/package.json) From: package-lock.json → npm/next@15.5.10 → npm/autoprefixer@10.4.14 → npm/jest@29.5.0 → npm/caniuse-lite@1.0.30001766 ℹ 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.30001766. 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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[augmentcode]

🤖 Augment PR Summary

Summary: This PR upgrades Next.js to address a high-severity Snyk-reported vulnerability.

Changes:

• Upgraded next from 13.1.6 to 15.5.10 in package.json
• Updated the npm lockfile (package-lock.json) to match the new dependency graph
• Applies the Snyk remediation for SNYK-JS-NEXT-15104645 (resource allocation / lack of throttling)

Technical Notes:

• This is a major-version Next.js upgrade and may introduce breaking changes across routing, caching defaults, and framework APIs
• Next.js 15 raises the minimum supported Node.js version (verify CI/runtime compatibility)
• Downstream Next ecosystem packages (lint config, auth, i18n integrations) may need verification for compatibility

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

next 15 requires Node.js >= 18.18.0 (per Next.js 15 release notes), but engines.node currently allows >=18.0.0, which could let CI/deploy run an unsupported Node version.

_{🤖 Was this useful? React with 👍 or 👎}

[augmentcode]

This upgrades next to 15.x but leaves eslint-config-next pinned at 13.1.6, which can lead to next lint/ESLint config incompatibilities; consider aligning eslint-config-next with the Next.js major version.

_{🤖 Was this useful? React with 👍 or 👎}

[gemini-code-assist]

Code Review

This pull request upgrades next from version 13.1.6 to 15.5.10 to fix a security vulnerability. This is a major version upgrade, which can introduce breaking changes. I've reviewed the dependency changes and found a few areas for improvement to ensure consistency and prevent potential issues. Specifically, I've recommended updating the related eslint-config-next package, aligning the Node.js engine requirement in your package.json, and fixing an inconsistency in the package-lock.json for the next dependency versioning.

[gemini-code-assist]

With the upgrade of next to a new major version, the eslint-config-next dev dependency should also be updated to match. It's currently on 13.1.6. Please update it to 15.5.10 in your devDependencies to ensure you have the correct linting rules for the new version of Next.js.

[gemini-code-assist]

This change in next's engine requirement is not reflected in the root package.json. The root engines.node is set to ">=18.0.0", which is not fully compatible with "^18.18.0 || ^19.8.0 || >= 20.0.0". This could lead to environment-specific issues where a developer's Node.js version satisfies the project's requirement but not next's. It's recommended to update the engines.node field in the root package.json to a compatible range, for example: "^18.18.0 || >=20.0.0".

[gemini-code-assist]

The package.json file specifies an exact version for next (15.5.10), but here in the lock file a caret range (^15.5.10) is used. This can lead to future npm install commands pulling a newer, potentially breaking, version of next. To ensure dependency stability, especially after a major version upgrade, this should be an exact version to match package.json. You can fix this by running npm install again or manually editing the line.

Suggested change

	"next": "^15.5.10",
	"next": "15.5.10",