Skip to content

Fix Node.js v18+ compatibility#94

Closed
legobeat wants to merge 0 commit intoMetaMask:mainfrom
legobeat:fix-nodejs-18-compat
Closed

Fix Node.js v18+ compatibility#94
legobeat wants to merge 0 commit intoMetaMask:mainfrom
legobeat:fix-nodejs-18-compat

Conversation

@legobeat
Copy link
Copy Markdown
Contributor

@legobeat legobeat commented Sep 1, 2023

@legobeat legobeat force-pushed the fix-nodejs-18-compat branch from 75878b0 to 020e4aa Compare September 1, 2023 05:45
@legobeat legobeat mentioned this pull request Sep 1, 2023
4 tasks
@socket-security
Copy link
Copy Markdown

socket-security Bot commented Sep 1, 2023

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue Package Version Note Source
Obfuscated require eslint-plugin-es 4.1.0
Obfuscated require resolve 1.22.4

Ignoring: for-each@0.3.3, functions-have-names@1.2.3, globalthis@1.0.3, available-typed-arrays@1.0.5, builtins@5.0.1, typed-array-length@1.0.4, es-shim-unscopables@1.0.0, natural-compare-lite@1.4.0, has-property-descriptors@1.0.0

Next steps

What is obfuscated require?

Package accesses dynamic properties of require and may be obfuscating code execution.

The package should not access dynamic properties of module. Instead use import or require directly.

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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore eslint-plugin-es@4.1.0
  • @SocketSecurity ignore resolve@1.22.4

@legobeat
Copy link
Copy Markdown
Contributor Author

legobeat commented Sep 1, 2023

@SocketSecurity ignore for-each@0.3.3
@SocketSecurity ignore functions-have-names@1.2.3
@SocketSecurity ignore globalthis@1.0.3
@SocketSecurity ignore available-typed-arrays@1.0.5
@SocketSecurity ignore builtins@5.0.1
@SocketSecurity ignore typed-array-length@1.0.4
@SocketSecurity ignore es-shim-unscopables@1.0.0
@SocketSecurity ignore natural-compare-lite@1.4.0
@SocketSecurity ignore has-property-descriptors@1.0.0
@SocketSecurity ignore eslint-plugin-n@15.7.0

@legobeat
Copy link
Copy Markdown
Contributor Author

This is resolved as of #90

@legobeat legobeat deleted the fix-nodejs-18-compat branch September 20, 2023 02:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant