Bump @types/node from 20.11.6 to 20.11.7 #71
Pull Request #71 Alerts: Complete with warnings
| Report | Status | Message |
|---|---|---|
| PR #71 Alerts | Found 1 project alert |
Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.
Details
🚨 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 |
|---|---|---|---|
| Chronological version anomaly | npm/@types/node@20.11.7 |
|
Next steps
What is a chronological version anomaly?
Semantic versions published out of chronological order.
This could either indicate dependency confusion or a patched vulnerability.
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/node@20.11.7