Skip to content
This repository has been archived by the owner on Mar 8, 2024. It is now read-only.

Bump @types/node from 20.10.8 to 20.11.20 #296

Closed
wants to merge 1 commit into from

Bump @types/node from 20.10.8 to 20.11.20

d05970f
Select commit
Loading
Failed to load commit list.
Closed

Bump @types/node from 20.10.8 to 20.11.20 #296

Bump @types/node from 20.10.8 to 20.11.20
d05970f
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts failed Feb 26, 2024 in 33s

Pull Request #296 Alerts: Complete with warnings WARNING: Free tier size exceeded

Report Status Message
PR #296 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 NoteSource
Install scripts npm/[email protected]
  • Install script: install
  • Source: node install/check

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.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all