Block |
 |
npm/@expo/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/@expo/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@expo/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@react-native-community/[email protected] has Shell access.
Module: child_process
Location: Package overview
From: yarn.lock → npm/@react-native-community/[email protected]
ℹ Read more on: This package | This alert | What is shell access?
Next steps: 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 [email protected] .
Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@react-native-community/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@react-native-community/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: package.json → npm/@react-native-community/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@react-native-community/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@react-native/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/@react-native/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@react-native/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@react-native/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/@react-native/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@react-native/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@react-native/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/@react-native/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@react-native/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@react-native/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/@react-native/[email protected] → npm/@react-native/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@react-native/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@react-native/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/@react-native/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@react-native/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@react-native/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/@react-native/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@react-native/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@react-native/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/@react-native/[email protected] → npm/@react-native/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@react-native/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@react-native/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/@react-native/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@react-native/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@sentry-internal/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/@sentry-internal/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@sentry-internal/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@sentry/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: package.json → npm/@sentry/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@sentry/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@viem/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: package.json → npm/@viem/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@viem/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@vscode/[email protected] has Shell access.
Module: child_process
Location: Package overview
From: yarn.lock → npm/@vscode/[email protected]
ℹ Read more on: This package | This alert | What is shell access?
Next steps: 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 [email protected] .
Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@vscode/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/[email protected] has Network access.
Module: globalThis["fetch"]
Location: Package overview
From: yarn.lock → npm/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/[email protected] has Native code.
Location: Package overview
From: yarn.lock → npm/[email protected]
ℹ Read more on: This package | This alert | Why is native code a concern?
Next steps: 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 [email protected] .
Suggestion: Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/[email protected] has Shell access.
Module: child_process
Location: Package overview
From: yarn.lock → npm/[email protected]
ℹ Read more on: This package | This alert | What is shell access?
Next steps: 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 [email protected] .
Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/[email protected] has Network access.
Module: net
Location: Package overview
From: yarn.lock → npm/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/[email protected] has Network access.
Module: http
Location: Package overview
From: yarn.lock → npm/[email protected]
ℹ Read more on: This package | This alert | What is network access?
Next steps: 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 [email protected] .
Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/[email protected] has Shell access.
Module: child_process
Location: Package overview
From: yarn.lock → npm/[email protected]
ℹ Read more on: This package | This alert | What is shell access?
Next steps: 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 [email protected] .
Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/[email protected] has Shell access.
Module: child_process
Location: Package overview
From: yarn.lock → npm/[email protected]
ℹ Read more on: This package | This alert | What is shell access?
Next steps: 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 [email protected] .
Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@expo/[email protected] has a New author.
New Author: evanbacon
Previous Author: brentvatne
From: yarn.lock → npm/@expo/[email protected]
ℹ Read more on: This package | This alert | What is new author?
Next steps: 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 [email protected] .
Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@expo/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/@sideway/[email protected] has a New author.
New Author: marsup
Previous Author: hueniverse
From: yarn.lock → npm/@sideway/[email protected]
ℹ Read more on: This package | This alert | What is new author?
Next steps: 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 [email protected] .
Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@sideway/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
Block |
 |
npm/[email protected] has a New author.
New Author: gabrieldonadel
Previous Author: lukmccall
From: yarn.lock → npm/[email protected]
ℹ Read more on: This package | This alert | What is new author?
Next steps: 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 [email protected] .
Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/[email protected] . You can
also ignore all packages with @SocketSecurity ignore-all .
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
|
See 6 more rows in the dashboard
|