[Snyk] Security upgrade next from 15.4.7 to 15.4.10

[Dargon789]

Snyk has created this PR to fix 3 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• extras/docs/package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Arbitrary Code Injection SNYK-JS-NEXT-14173355
	Deserialization of Untrusted Data SNYK-JS-NEXT-14400636
	Exposure of Sensitive System Information to an Unauthorized Control Sphere SNYK-JS-NEXT-14400644

---

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:

🦉 Arbitrary Code Injection

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
sequence-js-docs	Ready	Preview, Comment	Feb 4, 2026 1:56am
sequence-js-web	Ready	Preview, Comment	Feb 4, 2026 1:56am

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 14 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/dargon789-forge?upgradeToPro=build-rate-limit

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

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

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

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, 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, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the next dependency within the extras/docs package. This crucial update addresses multiple identified vulnerabilities, including critical and high-severity issues, thereby improving the overall robustness and security of the application. Manual intervention is required to update the pnpm-lock.yaml file.

Highlights

• Dependency Upgrade: The next dependency in extras/docs/package.json has been upgraded from ^15.4.8 to ^15.4.10.
• Security Vulnerabilities Addressed: This upgrade fixes 3 identified vulnerabilities: a critical Arbitrary Code Injection, a high-severity Deserialization of Untrusted Data, and a medium-severity Exposure of Sensitive System Information to an Unauthorized Control Sphere.
• Manual Action Required: The pnpm-lock.yaml file could not be updated automatically by Snyk and requires manual updating before merging this pull request.

Changelog

• extras/docs/package.json
  • Updated the next dependency version from ^15.4.8 to ^15.4.10.

Activity

• This pull request was automatically created by Snyk to address security vulnerabilities in the project's dependencies.
• Snyk identified 3 vulnerabilities in the next dependency that necessitated this upgrade.
• A warning was issued stating that the pnpm-lock.yaml file failed to update automatically and requires manual intervention.

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. ↩

[gemini-code-assist]

Code Review

This pull request from Snyk updates the next package to version ^15.4.10 to address several security vulnerabilities. While the update in package.json is correct, the PR is critically missing the corresponding update to pnpm-lock.yaml, as noted in the description. This must be fixed before merging to ensure the security patches are applied consistently across all environments and to prevent potential build inconsistencies.

[gemini-code-assist]

While updating the next dependency is correct, this pull request is incomplete because the pnpm-lock.yaml file was not updated. This is a critical issue that must be resolved before merging.

As Snyk's warning indicates, the lockfile needs to be regenerated. Running pnpm install will update the lock file based on this change. Without this step, you risk:

• Inconsistent Builds: Different developers and CI/CD environments might resolve and install different versions of next, potentially negating the security fix.
• Persistent Vulnerabilities: The old, vulnerable version might still be installed in some environments if they rely on an outdated lock file.

Please run pnpm install and commit the updated pnpm-lock.yaml to this branch before merging.