feat(examples): Next.js + Better Auth

[davidmytton]

Docs: arcjet/arcjet-docs#356

[trunk-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/[email protected]	None	0	9.48 kB	types
npm/@types/[email protected]	None	0	2.22 MB	types
npm/[email protected]	environment Transitive: network	+22	13.9 MB	bekacru
npm/[email protected]	Transitive: environment, filesystem, network	+16	10.3 MB	joshuawise
npm/[email protected]	environment, filesystem	+6	8.72 MB	adamwathan, malfaitrobin, reinink

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Network access	npm/[email protected]	Module: net Location: Package overview	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	🚫
Network access	npm/[email protected]	Module: tls Location: Package overview	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	🚫
Network access	npm/[email protected]	Module: http Location: Package overview	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	🚫
Network access	npm/[email protected]	Module: https Location: Package overview	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	🚫
Network access	npm/[email protected]	Module: http Location: Package overview	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	🚫
Network access	npm/[email protected]	Module: https Location: Package overview	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	🚫
Network access	npm/@better-fetch/[email protected]	Module: globalThis["fetch"] Location: Package overview	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	🚫
Network access	npm/[email protected]	Module: globalThis["fetch"] Location: Package overview	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	🚫
Network access	npm/@simplewebauthn/[email protected]	Module: globalThis["fetch"] Location: Package overview	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	🚫
Unstable ownership	npm/[email protected]	Author: ljharb	examples/nextjs-sensitive-info/package-lock.json examples/nextjs-sensitive-info/package.json	🚫
License Policy Violation	npm/[email protected]	License: CC-BY-4.0 - Not allowed by license policy (npm metadata, package/LICENSE, package/package.json)	examples/nextjs-authjs-5/package-lock.json examples/nextjs-authjs-5/package.json	⚠︎
Network access	npm/[email protected]	Module: globalThis["fetch"] Location: Package overview	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	🚫
License Policy Violation	npm/[email protected]	License: -- - No known license was found	examples/nextjs-better-auth/package-lock.json examples/nextjs-better-auth/package.json	⚠︎

View full report↗︎

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

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.

What is a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@better-fetch/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@simplewebauthn/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]

[davidmytton]

There may be a better way to do this @blaine-arcjet, but using ctx.request didn't match the types so I used our request helper instead.