vercel / next-learn

Learn Next.js Starter Code
https://next-learn-dashboard.vercel.sh/
MIT License
3.8k stars 1.93k forks source link

Update to Next 15 latest #888

Closed leerob closed 1 month ago

vercel[bot] commented 1 month ago

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

Name Status Preview Comments Updated (UTC)
next-learn-dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 8:36pm
next-learn-starter ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 8:36pm
next-seo-starter ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 8:36pm
socket-security[bot] commented 1 month ago

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

Package New capabilities Transitives Size Publisher
npm/react-dom@19.0.0-rc-cd22717c-20241013 environment +1 6.43 MB fb, gnoff, react-bot, ...2 more
npm/react@19.0.0-rc-cd22717c-20241013 environment 0 237 kB react-bot
npm/types-react-dom@19.0.0-rc.1 None 0 17.7 kB eps1lon
npm/types-react@19.0.0-rc.1 None +1 1.63 MB eps1lon

🚮 Removed packages: npm/@types/react-dom@18.3.0, npm/@types/react@18.3.3, npm/next@15.0.0-canary.56, npm/react-dom@19.0.0-rc-f38c22b244-20240704, npm/react@19.0.0-rc-f38c22b244-20240704

View full report↗︎

socket-security[bot] commented 1 month 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 NoteSourceCI
Possible typosquat attack npm/types-react-dom@19.0.0-rc.1 ⚠︎

View full report↗︎

Next steps

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/types-react-dom@19.0.0-rc.1