deps: update arcjet-js to v1.10.0-rc.0

[qw-in]

Updates all JavaScript and Deno examples to the Arcjet and Nosecone 1.10.0 release candidate, regenerating their independent lockfiles for release-candidate compatibility coverage.\n\nKeep this draft until the release is stable so the examples do not become a starting point for RC dependencies.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​arcjet/​react-router@​1.8.0 ⏵ 1.10.0-rc.0	+1		-1	+1
	npm/​@​arcjet/​fastify@​1.8.0 ⏵ 1.10.0-rc.0	+1		-1	+1
	npm/​@​arcjet/​nuxt@​1.8.0 ⏵ 1.10.0-rc.0			+1	-1
	npm/​@​arcjet/​sveltekit@​1.8.0 ⏵ 1.10.0-rc.0	+1		-1	+1
	npm/​@​arcjet/​nest@​1.8.0 ⏵ 1.10.0-rc.0	+1		-1	+1
	npm/​@​arcjet/​astro@​1.8.0 ⏵ 1.10.0-rc.0	+1			+1
	npm/​@​arcjet/​decorate@​1.8.0 ⏵ 1.10.0-rc.0				+1
	npm/​@​arcjet/​node@​1.8.0 ⏵ 1.10.0-rc.0	+1			+1
	npm/​@​arcjet/​inspect@​1.8.0 ⏵ 1.10.0-rc.0	+1			+1
	npm/​@​arcjet/​next@​1.8.0 ⏵ 1.10.0-rc.0				-1
	npm/​@​nosecone/​next@​1.8.0 ⏵ 1.10.0-rc.0				+1

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		Low adoption: npm @arcjet/astro Location: Package overview From: examples/astro/package-lock.json → npm/@arcjet/astro@1.10.0-rc.0 ℹ Read more on: This package | This alert | What are unpopular packages? 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: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/astro@1.10.0-rc.0. 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.
Warn		Low adoption: npm @arcjet/fastify Location: Package overview From: examples/fastify/package-lock.json → npm/@arcjet/fastify@1.10.0-rc.0 ℹ Read more on: This package | This alert | What are unpopular packages? 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: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/fastify@1.10.0-rc.0. 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.
Warn		Low adoption: npm @arcjet/nest Location: Package overview From: examples/nestjs/package-lock.json → npm/@arcjet/nest@1.10.0-rc.0 ℹ Read more on: This package | This alert | What are unpopular packages? 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: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/nest@1.10.0-rc.0. 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.
Warn		Low adoption: npm @arcjet/react-router Location: Package overview From: examples/react-router/package-lock.json → npm/@arcjet/react-router@1.10.0-rc.0 ℹ Read more on: This package | This alert | What are unpopular packages? 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: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/react-router@1.10.0-rc.0. 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.
Warn		Low adoption: npm @arcjet/sveltekit Location: Package overview From: examples/sveltekit/package-lock.json → npm/@arcjet/sveltekit@1.10.0-rc.0 ℹ Read more on: This package | This alert | What are unpopular packages? 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: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/sveltekit@1.10.0-rc.0. 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.
Warn		Network access: npm @arcjet/transport in module node:http Module: node:http Location: Package overview From: examples/nextjs-bot-protection/package-lock.json → npm/@arcjet/astro@1.10.0-rc.0 → npm/@arcjet/next@1.10.0-rc.0 → npm/@arcjet/nuxt@1.10.0-rc.0 → npm/@arcjet/fastify@1.10.0-rc.0 → npm/@arcjet/node@1.10.0-rc.0 → npm/@arcjet/nest@1.10.0-rc.0 → npm/@arcjet/react-router@1.10.0-rc.0 → npm/@arcjet/sveltekit@1.10.0-rc.0 → npm/@arcjet/transport@1.10.0-rc.0 ℹ Read more on: This package | This alert | What is network access? 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: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/transport@1.10.0-rc.0. 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.
Warn		Network access: npm @arcjet/transport in module node:https Module: node:https Location: Package overview From: examples/nextjs-bot-protection/package-lock.json → npm/@arcjet/astro@1.10.0-rc.0 → npm/@arcjet/next@1.10.0-rc.0 → npm/@arcjet/nuxt@1.10.0-rc.0 → npm/@arcjet/fastify@1.10.0-rc.0 → npm/@arcjet/node@1.10.0-rc.0 → npm/@arcjet/nest@1.10.0-rc.0 → npm/@arcjet/react-router@1.10.0-rc.0 → npm/@arcjet/sveltekit@1.10.0-rc.0 → npm/@arcjet/transport@1.10.0-rc.0 ℹ Read more on: This package | This alert | What is network access? 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: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/transport@1.10.0-rc.0. 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.
Warn		Network access: npm @arcjet/transport in module node:net Module: node:net Location: Package overview From: examples/nextjs-bot-protection/package-lock.json → npm/@arcjet/astro@1.10.0-rc.0 → npm/@arcjet/next@1.10.0-rc.0 → npm/@arcjet/nuxt@1.10.0-rc.0 → npm/@arcjet/fastify@1.10.0-rc.0 → npm/@arcjet/node@1.10.0-rc.0 → npm/@arcjet/nest@1.10.0-rc.0 → npm/@arcjet/react-router@1.10.0-rc.0 → npm/@arcjet/sveltekit@1.10.0-rc.0 → npm/@arcjet/transport@1.10.0-rc.0 ℹ Read more on: This package | This alert | What is network access? 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: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/transport@1.10.0-rc.0. 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.
Warn		Network access: npm @arcjet/transport in module node:tls Module: node:tls Location: Package overview From: examples/nextjs-bot-protection/package-lock.json → npm/@arcjet/astro@1.10.0-rc.0 → npm/@arcjet/next@1.10.0-rc.0 → npm/@arcjet/nuxt@1.10.0-rc.0 → npm/@arcjet/fastify@1.10.0-rc.0 → npm/@arcjet/node@1.10.0-rc.0 → npm/@arcjet/nest@1.10.0-rc.0 → npm/@arcjet/react-router@1.10.0-rc.0 → npm/@arcjet/sveltekit@1.10.0-rc.0 → npm/@arcjet/transport@1.10.0-rc.0 ℹ Read more on: This package | This alert | What is network access? 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: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/transport@1.10.0-rc.0. 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.
Warn		Filesystem access: npm @arcjet/astro with module node:fs/promises Module: node:fs/promises Location: Package overview From: examples/astro/package-lock.json → npm/@arcjet/astro@1.10.0-rc.0 ℹ Read more on: This package | This alert | What is filesystem access? 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: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/astro@1.10.0-rc.0. 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.
Warn		Filesystem access: npm @arcjet/nuxt with module node:fs/promises Module: node:fs/promises Location: Package overview From: examples/nuxt/package-lock.json → npm/@arcjet/nuxt@1.10.0-rc.0 ℹ Read more on: This package | This alert | What is filesystem access? 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: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/nuxt@1.10.0-rc.0. 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