Closed delbaoliveira closed 2 weeks ago
vercel[bot]
commented
2 weeks 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 | Jun 11, 2024 0:45am |
| next-learn-starter | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 11, 2024 0:45am |
| next-seo-starter | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 11, 2024 0:45am |
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/clsx@2.1.1 | None | 0 |
8.55 kB | lukeed |
| npm/dotenv@16.4.5 | environment, filesystem | 0 |
79.1 kB | motdotla |
| npm/eslint-config-next@15.0.0-rc.0 | unsafe Transitive: environment | +8 |
907 kB | vercel-release-bot |
| npm/eslint@8.57.0 | environment, filesystem | +1 |
3.09 MB | eslintbot |
| npm/next@15.0.0-rc.0 | environment, filesystem, network, shell, unsafe | +6 |
91.3 MB | vercel-release-bot |
| npm/prettier@3.3.0 | environment, filesystem, unsafe | 0 |
8.25 MB | prettier-bot |
| npm/prettier@3.3.2 | None | 0 |
0 B | |
| npm/react-dom@19.0.0-rc-6230622a1a-20240610 | None | 0 |
0 B | |
| npm/react@19.0.0-rc-6230622a1a-20240610 | None | 0 |
0 B | |
| npm/zod@3.23.8 | None | 0 |
667 kB | colinmcd94 |
🚮 Removed packages: npm/next-auth@5.0.0-beta.3, npm/next@14.0.2, npm/use-debounce@9.0.4, npm/zod@3.22.4
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.
(Experimental) Copyleft license information was found
Determine whether use of copyleft material works for you
(Experimental) A license not known to be considered permissive was found
Determine whether use of material not offered under a known permissive license works for you
Contains a high severity Common Vulnerability and Exposure (CVE).
Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
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.
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.
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/@img/sharp-libvips-linuxmusl-x64@1.0.2@SocketSecurity ignore npm/@img/sharp-libvips-linux-x64@1.0.2@SocketSecurity ignore npm/@img/sharp-libvips-darwin-arm64@1.0.2@SocketSecurity ignore npm/@img/sharp-libvips-darwin-x64@1.0.2@SocketSecurity ignore npm/@img/sharp-libvips-linux-arm@1.0.2@SocketSecurity ignore npm/@img/sharp-libvips-linux-arm64@1.0.2@SocketSecurity ignore npm/@img/sharp-libvips-linux-s390x@1.0.2@SocketSecurity ignore npm/@img/sharp-libvips-linuxmusl-arm64@1.0.2@SocketSecurity ignore npm/@img/sharp-wasm32@0.33.4@SocketSecurity ignore npm/@img/sharp-win32-ia32@0.33.4@SocketSecurity ignore npm/@img/sharp-win32-x64@0.33.4@SocketSecurity ignore npm/braces@3.0.2@SocketSecurity ignore npm/spdx-exceptions@2.3.0@SocketSecurity ignore npm/next@14.0.2
Update the dashboard example to newer versions, and switch to
pnpmdue to errors withnpm. Despitenpmbeing more popular, we prefer and usepnpmeverywhere.Also, unlike
npmwhich prevents updating versions,pnpmwill warn of unmet peer dependencies. This approach is better than telling beginners to add--legacy-peers-depsor--forcewhen usingnpm. We'll update versions again when Next.js 15 is stable. This will allow us to start teaching more PPR.