search

nextauthjs / next-auth

Authentication for the Web.
https://authjs.dev
ISC License
22.49k stars 2.98k forks source link

Allow peer-installing svelte 5 preview #10771

Closed nathanblair closed 2 weeks ago

nathanblair commented 2 weeks ago

Fixes: #10770

☕️ Reasoning

GitHub bot keeps closing my issues (seriously, please fix that) - but this should go some way in addressing that problem.

🧢 Checklist

🎫 Affected issues

📌 Resources

vercel[bot] commented 2 weeks ago

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

Name Status Preview Comments Updated (UTC)
auth-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 30, 2024 3:09am
1 Ignored Deployment | Name | Status | Preview | Comments | Updated (UTC) | | :--- | :----- | :------ | :------- | :------ | | **next-auth-docs** | ⬜️ Ignored ([Inspect](https://vercel.com/authjs/next-auth-docs/Ab1bTwXXK2AkpREkNHz9ET7s4SnY)) | [Visit Preview](https://next-auth-docs-git-fork-nathanblair-patch-2-authjs.vercel.app) | | Apr 30, 2024 3:09am |
vercel[bot] commented 2 weeks ago

@nathanblair is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

socket-security[bot] commented 2 weeks ago

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

Package New capabilities Transitives Size Publisher
npm/@solid-auth/next@0.0.19 environment Transitive: network +6 1.38 MB orjdev
npm/@solidjs/meta@0.28.7 None 0 20.4 kB ryansolid
npm/@solidjs/router@0.6.0 None 0 87.6 kB ryansolid
npm/@types/node@18.19.31 None 0 1.97 MB types
npm/@types/react-dom@18.3.0 None 0 37.8 kB types
npm/@types/react@18.3.1 None 0 438 kB types
npm/clsx@2.1.1 None 0 8.55 kB lukeed
npm/next@14.2.3 environment, filesystem, network, shell, unsafe +13 1.2 GB vercel-release-bot
npm/react-dom@18.3.1 environment +1 4.61 MB react-bot
npm/react@18.3.1 environment 0 318 kB react-bot
npm/solid-js@1.8.17 None +2 2.07 MB ryansolid
npm/solid-start-node@0.2.32 environment, filesystem Transitive: network, unsafe +43 5.34 MB ryansolid
npm/solid-start-vercel@0.2.32 filesystem, shell Transitive: environment, eval, network, unsafe +75 6.4 MB ryansolid
npm/solid-start@0.2.32 Transitive: environment, eval, filesystem, network, shell, unsafe +314 445 MB ryansolid
npm/typescript@5.2.2 None 0 40.6 MB typescript-bot
npm/vite@3.2.10 environment, eval, filesystem, network, shell, unsafe +24 202 MB vitebot

🚮 Removed packages: npm/@types/node@20.12.7

View full report↗︎

socket-security[bot] commented 2 weeks ago

🚨 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 NoteSource
Install scripts npm/esbuild@0.15.18
Install scripts npm/esbuild@0.17.19
Install scripts npm/esbuild@0.18.20
Potential typo squat npm/esbuild-plugin-solid@0.5.0

View full report↗︎

Next steps

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 a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/esbuild@0.15.18
  • @SocketSecurity ignore npm/esbuild@0.17.19
  • @SocketSecurity ignore npm/esbuild@0.18.20
  • @SocketSecurity ignore npm/esbuild-plugin-solid@0.5.0
nathanblair commented 2 weeks ago

I think this would actually be something better solved through package.json overrides. My mistake - I haven't been in the npm world for a long time!