Dependency updates

[aarongoldenthal]

No description provided.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	2.44 MB	npmdeque
npm/[email protected]	environment, filesystem, shell	0	181 kB	abetomo
npm/[email protected]	environment, eval, filesystem, shell	0	162 kB	tabrindle
npm/[email protected]	filesystem Transitive: environment, eval, network, shell, unsafe	+360	68.6 MB	simenb
npm/[email protected]	environment, filesystem Transitive: eval, shell, unsafe	+97	10.8 MB	eslintbot
npm/[email protected]	environment Transitive: filesystem, network, shell, unsafe	+117	59.2 MB	google-wombot
npm/[email protected]	None	+2	125 kB	npm-cli-ops

🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

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
Unmaintained	npm/[email protected]	Last Publish: 9/10/2018, 7:02:16 PM	package-lock.json package.json
Dynamic require	npm/[email protected]	Location: Package overview	package-lock.json package.json
Environment variable access	npm/@typescript-eslint/[email protected]	Env Vars: TSESTREE_NO_INVALIDATION Location: Package overview	package-lock.json package.json
Environment variable access	npm/@typescript-eslint/[email protected]	Env Vars: CI Location: Package overview	package-lock.json package.json
Environment variable access	npm/@typescript-eslint/[email protected]	Env Vars: TSESTREE_SINGLE_RUN Location: Package overview	package-lock.json package.json
Unmaintained	npm/[email protected]	Last Publish: 2/13/2017, 5:14:56 PM	package-lock.json package.json
Filesystem access	npm/[email protected]	Module: fs/promises Location: Package overview	package-lock.json package.json
Environment variable access	npm/[email protected]	Env Vars: BROWSERSLIST_ROOT_PATH Location: Package overview	package-lock.json package.json
Environment variable access	npm/[email protected]	Env Vars: name Location: Package overview	package-lock.json package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.mjs	package-lock.json package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	package-lock.json package.json
Shell access	npm/[email protected]	Module: child_process Location: Package overview	package-lock.json package.json

View full report↗︎

Next steps

What are unmaintained packages?

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.

What is dynamic require?

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.

What is environment variable access?

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.

What is filesystem access?

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.

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.

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.

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/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@typescript-eslint/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]