[Snyk] Security upgrade @arcjet/next from 1.0.0-beta.9 to 1.1.0

[Dargon789]

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-UNDICI-14943963	336

---

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	Actions	Updated (UTC)
arcjet-example	Error		Feb 7, 2026 3:02am
arcjet-example-pvhg	Error		Feb 7, 2026 3:02am

[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, performs a critical security upgrade for the @arcjet/next package and its ecosystem of related dependencies. The primary goal is to mitigate a known vulnerability and ensure the project benefits from the latest stable releases, which includes updating Node.js engine requirements for improved compatibility and performance.

Highlights

• Security Vulnerability Fix: This pull request addresses and fixes one vulnerability, 'Allocation of Resources Without Limits or Throttling' (SNYK-JS-UNDICI-14943963), by upgrading the @arcjet/next package.
• Dependency Upgrade: The @arcjet/next package has been upgraded from version 1.0.0-beta.9 to 1.1.0. This also triggered updates for numerous other @arcjet related dependencies (e.g., @arcjet/analyze, @arcjet/duration, @arcjet/headers, @arcjet/logger, @arcjet/stable-hash, @arcjet/transport, and arcjet) to their 1.1.0 versions.
• Node.js Engine Requirement Update: The minimum Node.js version required for several @arcjet packages has been increased from >=18 to >=20, ensuring compatibility with newer runtime features and security patches.
• Dependency Graph Refinement: The package-lock.json file shows a restructuring of dependencies, including the removal of direct entries for @connectrpc/connect-node, @connectrpc/connect-web, @fastify/busboy, and undici, suggesting these are now managed as sub-dependencies or are no longer directly required.
• Development Dependency Flagging: Several optional development dependencies within package-lock.json have been explicitly marked with "dev": true, clarifying their role in the project's build and development process.

Changelog

• package-lock.json
  • Updated @arcjet/next to ^1.1.0.
  • Upgraded various @arcjet packages (e.g., @arcjet/analyze, @arcjet/analyze-wasm, @arcjet/duration, @arcjet/headers, @arcjet/logger, @arcjet/stable-hash, @arcjet/transport, arcjet) from 1.0.0-beta.9 to 1.1.0.
  • Increased the minimum Node.js engine requirement for several @arcjet packages from >=18 to >=20.
  • Introduced new nested dependencies under @arcjet/analyze, @arcjet/logger, @arcjet/next, and arcjet for @arcjet/cache, @arcjet/protocol, @bufbuild/protobuf, and @connectrpc/connect.
  • Removed direct node_modules entries for @connectrpc/connect-node, @connectrpc/connect-web, @fastify/busboy, and undici.
  • Added "dev": true flag to several optional development dependencies such as @parcel/watcher, braces, detect-libc, fill-range, fsevents, is-extglob, is-glob, is-number, micromatch, node-addon-api, picomatch, and to-regex-range.
• package.json
  • Updated @arcjet/next dependency from 1.0.0-beta.9 to 1.1.0.

Activity

• Snyk automatically created this pull request to address and fix 1 vulnerability in the project's npm dependencies.

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

The pull request successfully upgrades @arcjet/next to version 1.1.0, which addresses the undici vulnerability as intended. However, there are a few points regarding dependency consistency that should be addressed. Specifically, there is a version mismatch between @arcjet/next and other explicitly listed @arcjet utility dependencies in package.json, which can lead to dependency duplication. Additionally, a discrepancy was found between the pinned version in package.json and the caret version used in package-lock.json.

[gemini-code-assist]

There is a discrepancy between package.json and package-lock.json. In package.json, @arcjet/next is pinned to 1.1.0, but here it is specified with a caret as ^1.1.0. To ensure consistent builds and adhere to the project's dependency pinning strategy, this should be changed to match the pinned version.

Suggested change

	"@arcjet/next": "^1.1.0",
	"@arcjet/next": "1.1.0",