devDeps: [email protected]>~0.72.14

[legobeat]

Bump react-native and peers to 0.72, unpin to minor version.

Related

• chore: Bump example app to 0.73 and use babel to build react-native-webview/react-native-webview#3347

Blocked by

• devDeps: appium@^1.22.3->^2.5.4 #30
• devDeps: [email protected]>^18.3.1 #28
• ci: run all jobs on node 20 #32

[socket-security]

Report too large to display inline

View full report↗︎

[socket-security]

🚨 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
Deprecated	npm/@babel/[email protected]	Reason: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.	yarn.lock	⚠︎
Network access	npm/@azure/[email protected]	Module: http Location: Package overview	yarn.lock	🚫
Network access	npm/@azure/[email protected]	Module: https Location: Package overview	yarn.lock	🚫
Network access	npm/@azure/[email protected]	Module: https-proxy-agent Location: Package overview	yarn.lock	🚫
Network access	npm/@azure/[email protected]	Module: http-proxy-agent Location: Package overview	yarn.lock	🚫
Network access	npm/@azure/[email protected]	Module: https-proxy-agent Location: Package overview	yarn.lock	🚫
Network access	npm/@azure/[email protected]	Module: http-proxy-agent Location: Package overview	yarn.lock	🚫
Network access	npm/@azure/[email protected]	Module: http Location: Package overview	yarn.lock	🚫
Network access	npm/@azure/[email protected]	Module: https Location: Package overview	yarn.lock	🚫
New author	npm/[email protected]	New Author: flowtype Previous Author: gkz	yarn.lock	🚫
Shell access	npm/@react-native-community/[email protected]	Module: child_process Location: Package overview	yarn.lock	🚫
AI warning	npm/@react-native-community/[email protected]	Notes: The code is generally intended for shortcut creation but poses a security risk due to its method of executing a VBScript file that could be manipulated or misused. External command execution increases the risk. No immediate signs of malicious intent, but the approach has inherent risks and could potentially be leveraged for harmful purposes if input is not properly sanitized or secured. Confidence: 1.00 Severity: 0.60	yarn.lock	⚠︎
Shell access	npm/@react-native-community/[email protected]	Module: child_process Location: Package overview	yarn.lock	🚫
Shell access	npm/@opentelemetry/[email protected]	Module: child_process Location: Package overview	yarn.lock	🚫
Shell access	npm/@opentelemetry/[email protected]	Module: child_process Location: Package overview	yarn.lock	🚫
Network access	npm/[email protected]	Module: globalThis["fetch"] Location: Package overview	package.json yarn.lock	🚫

Ignoring: npm/@react-native/[email protected]

View full report↗︎

Next steps

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

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.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is an AI-detected potential code anomaly?

AI has identified unusual behaviors that may pose a security risk.

An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

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

• @SocketSecurity ignore npm/@babel/[email protected]
• @SocketSecurity ignore npm/@azure/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@react-native-community/[email protected]
• @SocketSecurity ignore npm/@react-native-community/[email protected]
• @SocketSecurity ignore npm/@opentelemetry/[email protected]
• @SocketSecurity ignore npm/[email protected]

[legobeat]

@SocketSecurity ignore npm/[email protected]

shell access, install scripts ok

[legobeat]

@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/@appium/[email protected]

network access ok

[legobeat]

@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/[email protected]

shell access ok

[legobeat]

@SocketSecurity ignore npm/@react-native/[email protected]
@SocketSecurity ignore npm/[email protected]

new authors ok

[leotm]

noting example app changes to check: https://react-native-community.github.io/upgrade-helper/?from=0.71.12&to=0.72.14&package=WebviewExample&name=com.reactnativecommunity.webview

[leotm]

best we stick to zulu@11 for RN 0.72
then introduce JDK 17 in RN 0.73
like upstream

[legobeat]

@joaoloureirop @kylanhurt any ideas/thoughts on this one?