chore(deps): update JavaScript examples to Arcjet 1.12.0

[qw-in]

We recently released version 1.12.0 of our JavaScript SDK. This gets us up to date

[arcjet-review]

Arcjet Review — 🔴 High Risk

Decision: Cannot Assess

Rationale: Review failed due to an internal error: unknown error. Escalating to human reviewers.

_{Review: 5a6c0a30 | Powered by Arcjet Review}

[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/​sensitive-info-rampart@​1.11.0 ⏵ 1.12.0				+1
	npm/​@​arcjet/​react-router@​1.11.0 ⏵ 1.12.0	+1		+1
	npm/​@​arcjet/​fastify@​1.11.0 ⏵ 1.12.0			+1
	npm/​@​arcjet/​sveltekit@​1.11.0 ⏵ 1.12.0			+1
	npm/​@​arcjet/​nuxt@​1.11.0 ⏵ 1.12.0			+1
	npm/​@​arcjet/​bun@​1.11.0 ⏵ 1.12.0	+1		+1
	npm/​@​arcjet/​astro@​1.11.0 ⏵ 1.12.0			+1
	npm/​@​arcjet/​nest@​1.11.0 ⏵ 1.12.0
	npm/​@​arcjet/​decorate@​1.11.0 ⏵ 1.12.0	-1
	npm/​@​arcjet/​guard@​1.11.0 ⏵ 1.12.0	+1
	npm/​@​arcjet/​inspect@​1.11.0 ⏵ 1.12.0	+3
	npm/​@​arcjet/​node@​1.11.0 ⏵ 1.12.0	+1
	npm/​@​nosecone/​next@​1.11.0 ⏵ 1.12.0
	npm/​@​arcjet/​next@​1.11.0 ⏵ 1.12.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		Publisher changed: npm @arcjet/analyze is now published by quinn-arcjet Author: quinn-arcjet From: examples/tanstack-start/package-lock.json → npm/@arcjet/astro@1.12.0 → npm/@arcjet/fastify@1.12.0 → npm/@arcjet/guard@1.12.0 → npm/@arcjet/nest@1.12.0 → npm/@arcjet/next@1.12.0 → npm/@arcjet/node@1.12.0 → npm/@arcjet/nuxt@1.12.0 → npm/@arcjet/react-router@1.12.0 → npm/@arcjet/sveltekit@1.12.0 → npm/@arcjet/sensitive-info-rampart@1.12.0 → npm/@arcjet/analyze@1.12.0 ℹ Read more on: This package | This alert | What is unstable ownership? 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: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/analyze@1.12.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		License policy violation: npm @arcjet/sensitive-info-rampart under CC-BY-4.0 License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/models/rampart/LICENSE) From: examples/nextjs-sensitive-info/package-lock.json → npm/@arcjet/sensitive-info-rampart@1.12.0 ℹ 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/@arcjet/sensitive-info-rampart@1.12.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		Publisher changed: npm arcjet is now published by quinn-arcjet Author: quinn-arcjet From: examples/tanstack-start/package-lock.json → npm/@arcjet/astro@1.12.0 → npm/@arcjet/bun@1.12.0 → npm/@arcjet/fastify@1.12.0 → npm/@arcjet/nest@1.12.0 → npm/@arcjet/next@1.12.0 → npm/@arcjet/node@1.12.0 → npm/@arcjet/nuxt@1.12.0 → npm/@arcjet/react-router@1.12.0 → npm/@arcjet/sveltekit@1.12.0 → npm/@arcjet/sensitive-info-rampart@1.12.0 → npm/arcjet@1.12.0 ℹ Read more on: This package | This alert | What is unstable ownership? 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: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/arcjet@1.12.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.12.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.12.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		Publisher changed: npm @arcjet/analyze is now published by quinn-arcjet instead of GitHub Actions New Author: quinn-arcjet Previous Author: [GitHub Actions](https://socket.dev/npm/user/GitHub Actions) From: examples/tanstack-start/package-lock.json → npm/@arcjet/astro@1.12.0 → npm/@arcjet/fastify@1.12.0 → npm/@arcjet/guard@1.12.0 → npm/@arcjet/nest@1.12.0 → npm/@arcjet/next@1.12.0 → npm/@arcjet/node@1.12.0 → npm/@arcjet/nuxt@1.12.0 → npm/@arcjet/react-router@1.12.0 → npm/@arcjet/sveltekit@1.12.0 → npm/@arcjet/sensitive-info-rampart@1.12.0 → npm/@arcjet/analyze@1.12.0 ℹ Read more on: This package | This alert | What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@arcjet/analyze@1.12.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		Publisher changed: npm arcjet is now published by quinn-arcjet instead of GitHub Actions New Author: quinn-arcjet Previous Author: [GitHub Actions](https://socket.dev/npm/user/GitHub Actions) From: examples/tanstack-start/package-lock.json → npm/@arcjet/astro@1.12.0 → npm/@arcjet/bun@1.12.0 → npm/@arcjet/fastify@1.12.0 → npm/@arcjet/nest@1.12.0 → npm/@arcjet/next@1.12.0 → npm/@arcjet/node@1.12.0 → npm/@arcjet/nuxt@1.12.0 → npm/@arcjet/react-router@1.12.0 → npm/@arcjet/sveltekit@1.12.0 → npm/@arcjet/sensitive-info-rampart@1.12.0 → npm/arcjet@1.12.0 ℹ Read more on: This package | This alert | What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/arcjet@1.12.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

[arcjet-review]

Arcjet Review — 🔴 High Risk

Decision: Cannot Assess

Rationale: Review failed due to an internal error: unknown error. Escalating to human reviewers.

_{Review: ea2325d9 | Powered by Arcjet Review}