Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency.

Removing this package as a dependency and implementing its logic will reduce supply chain risk.

Package has not been updated in more than 5 years and may be unmaintained. Problems with the package may go unaddressed.

Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use eval, since this could potentially execute any code.

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.

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.

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.

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.

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.

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/has-flag@3.0.0
• @SocketSecurity ignore npm/safer-buffer@2.1.2
• @SocketSecurity ignore npm/is-number@7.0.0
• @SocketSecurity ignore npm/depd@2.0.0
• @SocketSecurity ignore npm/destroy@1.2.0
• @SocketSecurity ignore npm/etag@1.8.1
• @SocketSecurity ignore npm/mime@1.6.0
• @SocketSecurity ignore npm/parseurl@1.3.3
• @SocketSecurity ignore npm/range-parser@1.2.1
• @SocketSecurity ignore npm/unpipe@1.0.0
• @SocketSecurity ignore npm/utils-merge@1.0.1
• @SocketSecurity ignore npm/path-is-absolute@1.0.1
• @SocketSecurity ignore npm/object-assign@4.1.1
• @SocketSecurity ignore npm/@aws-sdk/is-array-buffer@3.201.0
• @SocketSecurity ignore npm/@aws-sdk/credential-provider-web-identity@3.208.0
• @SocketSecurity ignore npm/@aws-sdk/shared-ini-file-loader@3.208.0
• @SocketSecurity ignore npm/aws-crt@1.21.2
• @SocketSecurity ignore npm/@smithy/node-config-provider@3.1.0