Closed vojtaholik closed 3 months ago
The latest updates on your projects. Learn more about Vercel for Git βοΈ
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
course-builder-docs | β Ready (Inspect) | Visit Preview | π¬ Add feedback | Jul 19, 2024 7:07am |
course-builder-poc | β Ready (Inspect) | Visit Preview | π¬ Add feedback | Jul 19, 2024 7:07am |
course-builder-video-blog | β Ready (Inspect) | Visit Preview | π¬ Add feedback | Jul 19, 2024 7:07am |
epic-web-v2 | β Ready (Inspect) | Visit Preview | π¬ Add feedback | Jul 19, 2024 7:07am |
pro-aws | β Ready (Inspect) | Visit Preview | π¬ Add feedback | Jul 19, 2024 7:07am |
pro-nextjs | β Ready (Inspect) | Visit Preview | π¬ Add feedback | Jul 19, 2024 7:07am |
value-based-design | β Ready (Inspect) | Visit Preview | π¬ Add feedback | Jul 19, 2024 7:07am |
π¨ 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 |
---|---|---|---|---|
Telemetry | npm/next@14.2.3 |
|
| π« |
This package contains telemetry which tracks how it is used.
Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked.
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/next@14.2.3