Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dependency react-router-dom to v6 #58

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Update dependency react-router-dom to v6

56c364a
Select commit
Failed to load commit list.
Open

Update dependency react-router-dom to v6 #58

Update dependency react-router-dom to v6
56c364a
Select commit
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts failed May 10, 2024 in 1m 28s

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

Report Status Message
PR #58 Alerts ⚠️ Found 3 project alerts

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/ngrok@3.2.7
  • Install script: postinstall
  • Source: node ./postinstall.js
Install scripts npm/node-sass@7.0.2
  • Install script: install
  • Source: node scripts/install.js
Install scripts npm/node-sass@7.0.2
  • Install script: postinstall
  • Source: node scripts/build.js

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/ngrok@3.2.7
  • @SocketSecurity ignore npm/node-sass@7.0.2
View more details on Socket Security