chore(deps): bump braces from 3.0.2 to 3.0.3

🚨 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/rc@1.2.8	Last Publish: 5/26/2018, 11:43:53 PM	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/rc@1.2.8	Env Vars: HOME Location: Package overview	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/rc@1.2.8	Env Vars: USERPROFILE Location: Package overview	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/rc@1.2.8	Env Vars: Location: Package overview	`package.json` `pnpm-lock.yaml`
Filesystem access	npm/rc@1.2.8	Module: fs Location: Package overview	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/is-unicode-supported@1.3.0	Env Vars: TERMINUS_SUBLIME Location: Package overview	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/is-unicode-supported@1.3.0	Env Vars: TERM Location: Package overview	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/is-unicode-supported@1.3.0	Env Vars: CI Location: Package overview	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/is-unicode-supported@1.3.0	Env Vars: WT_SESSION Location: Package overview	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/is-unicode-supported@1.3.0	Env Vars: ConEmuTask Location: Package overview	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/is-unicode-supported@1.3.0	Env Vars: TERM_PROGRAM Location: Package overview	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/is-unicode-supported@1.3.0	Env Vars: TERMINAL_EMULATOR Location: Package overview	`package.json` `pnpm-lock.yaml`
Environment variable access	npm/registry-auth-token@5.0.2	Env Vars: envVar Location: Package overview	`package.json` `pnpm-lock.yaml`
Uses eval	npm/bottleneck@2.19.5	Eval Type: eval Location: Package overview	`package.json` `pnpm-lock.yaml`
New author	npm/get-stream@8.0.1	New Author: ehmicky Previous Author: sindresorhus	`package.json` `pnpm-lock.yaml`
Filesystem access	npm/conventional-changelog-writer@7.0.1	Module: fs/promises Location: Package overview	`package.json` `pnpm-lock.yaml`
Deprecated	npm/read-pkg-up@11.0.0	Reason: Renamed to read-package-up	`package.json` `pnpm-lock.yaml`
Unmaintained	npm/object-keys@1.1.1	Last Publish: 4/7/2019, 2:30:18 AM	Source
Trivial Package	npm/isarray@2.0.5	Location: Package overview	Source
Unmaintained	npm/get-caller-file@2.0.5	Last Publish: 3/9/2019, 9:48:30 PM	Source
Filesystem access	npm/require-directory@2.1.1	Module: fs Location: Package overview	Source
Unmaintained	npm/require-directory@2.1.1	Last Publish: 5/28/2015, 8:31:04 AM	Source
Filesystem access	npm/y18n@5.0.8	Module: fs Location: Package overview	Source
Unmaintained	npm/media-typer@0.3.0	Last Publish: 4/25/2019, 3:16:05 AM	Source
Unmaintained	npm/for-each@0.3.3	Last Publish: 6/2/2018, 5:30:56 AM	Source
New author	npm/for-each@0.3.3	New Author: ljharb Previous Author: raynos	Source
Trivial Package	npm/min-indent@1.0.1	Location: Package overview	Source
Environment variable access	npm/config-chain@1.1.13	Env Vars: Location: Package overview	Source
Filesystem access	npm/config-chain@1.1.13	Module: fs Location: Package overview	Source
Network access	npm/config-chain@1.1.13	Module: http Location: Package overview	Source
Unmaintained	npm/proto-list@1.2.4	Last Publish: 5/21/2015, 12:58:33 AM	Source

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 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 eval?

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.

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 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 are trivial packages?

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.

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.

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

@SocketSecurity ignore npm/rc@1.2.8
@SocketSecurity ignore npm/is-unicode-supported@1.3.0
@SocketSecurity ignore npm/registry-auth-token@5.0.2
@SocketSecurity ignore npm/bottleneck@2.19.5
@SocketSecurity ignore npm/get-stream@8.0.1
@SocketSecurity ignore npm/conventional-changelog-writer@7.0.1
@SocketSecurity ignore npm/read-pkg-up@11.0.0
@SocketSecurity ignore npm/object-keys@1.1.1
@SocketSecurity ignore npm/isarray@2.0.5
@SocketSecurity ignore npm/get-caller-file@2.0.5
@SocketSecurity ignore npm/require-directory@2.1.1
@SocketSecurity ignore npm/y18n@5.0.8
@SocketSecurity ignore npm/media-typer@0.3.0
@SocketSecurity ignore npm/for-each@0.3.3
@SocketSecurity ignore npm/min-indent@1.0.1
@SocketSecurity ignore npm/config-chain@1.1.13
@SocketSecurity ignore npm/proto-list@1.2.4

ducktors / turborepo-remote-cache

chore(deps): bump braces from 3.0.2 to 3.0.3 #385

Next steps