Skip to content

[Snyk] Security upgrade next from 15.5.11 to 16.1.5 - #78

Closed
Dargon789 wants to merge 1 commit into
mainfrom
snyk-fix-2cea2c7b47cc4519169049611438b0d3
Closed

Dargon789 wants to merge 1 commit into
mainfrom
snyk-fix-2cea2c7b47cc4519169049611438b0d3

Conversation

@Dargon789

Copy link
Copy Markdown
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/create-onchain/templates/minikit-snake/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-NEXT-15105315
  696  

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

…reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-NEXT-15105315
@vercel

vercel Bot commented Jan 30, 2026

Copy link
Copy Markdown

Deployment failed with the following error:

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

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

@snyk-io

snyk-io Bot commented Jan 30, 2026

Copy link
Copy Markdown

✅ 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

Copy link
Copy Markdown

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist1! 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, updates the next dependency to a newer version to mitigate a critical security vulnerability. The change specifically targets the minikit-snake template within the create-onchain package, ensuring that projects initialized with this template are more secure against potential resource exhaustion attacks.

Highlights

  • Dependency Update: The next dependency has been updated from ^15.3.3 to ^16.1.5 in packages/create-onchain/templates/minikit-snake/package.json.
  • Security Vulnerability Fix: This update resolves a high-severity "Allocation of Resources Without Limits or Throttling" vulnerability (SNYK-JS-NEXT-15105315) found in the next package.
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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request from Snyk upgrades the next dependency to version 16.1.5 in the minikit-snake template to resolve a security vulnerability. While this is a necessary change, it appears to be incomplete. The eslint-config-next package also needs to be updated to a compatible version to avoid build and linting issues. Furthermore, other templates in this repository (minikit-basic, next) are still using older, vulnerable versions of next. I recommend updating next and its related dependencies across all relevant templates to ensure consistency and fully address the security risk.

"@farcaster/frame-sdk": "^0.0.60",
"@upstash/redis": "^1.34.4",
"next": "^15.3.3",
"next": "^16.1.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

With this major version upgrade of next, the eslint-config-next dependency in devDependencies (line 27) should also be updated from 15.3.3 to a version compatible with next@16, such as 16.1.5. This will prevent potential linting errors and ensure the ESLint configuration aligns with the new Next.js version.

@github-actions

github-actions Bot commented Apr 1, 2026

Copy link
Copy Markdown

Stale pull request message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants