feat: Better Auth integration

[davidmytton]

Depends on arcjet/arcjet-js#2750

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
arcjet-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 8, 2025 9:28am

[socket-security]

New and removed 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/[email protected]	environment Transitive: network	+28	15 MB	bekacru
npm/[email protected]	Transitive: environment, filesystem, network, shell	+37	10.9 MB	joshuawise

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	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: tls Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: http Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: https Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: https Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: http Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: https Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: tls Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: http Location: Package overview	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: net Location: Package overview	package-lock.json package.json	🚫
Network access	npm/@better-fetch/[email protected]	Module: globalThis["fetch"] Location: Package overview	package-lock.json package.json	🚫
Install scripts	npm/@parcel/[email protected]	Install script: install Source: node scripts/build-from-source.js	package-lock.json package.json	🚫
Shell access	npm/@parcel/[email protected]	Module: child_process Location: Package overview	package-lock.json package.json	🚫
Native code	npm/@parcel/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Unstable ownership	npm/@vscode/[email protected]	Author: microsoft1es	package-lock.json package.json	🚫
New author	npm/@vscode/[email protected]	New Author: microsoft1es Previous Author: vscode-bot	package-lock.json package.json	🚫
Unstable ownership	npm/[email protected]	Author: microsoft1es	package-lock.json package.json	🚫
New author	npm/[email protected]	New Author: microsoft1es Previous Author: vscode-bot	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: globalThis["fetch"] Location: Package overview	package-lock.json package.json	🚫
Network access	npm/@simplewebauthn/[email protected]	Module: globalThis["fetch"] Location: Package overview	package-lock.json package.json	🚫
Unstable ownership	npm/[email protected]	Author: ljharb	package-lock.json package.json	🚫
Network access	npm/[email protected]	Module: globalThis["fetch"] Location: Package overview	package-lock.json package.json	🚫
License Policy Violation	npm/[email protected]	License: -- - No known license was found	package-lock.json 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 an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

Why is native code a concern?

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks.

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 new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

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.

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/[email protected]
• @SocketSecurity ignore npm/@better-fetch/[email protected]
• @SocketSecurity ignore npm/@parcel/[email protected]
• @SocketSecurity ignore npm/@vscode/[email protected]
• @SocketSecurity ignore npm/[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]