[Snyk] Security upgrade rimraf from 3.0.2 to 4.0.0

[naiba4]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • packages/env/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	Yes	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
gutenberg	❌ Failed (Inspect)			Nov 30, 2023 8:21pm
gutenberg-wd9x	❌ Failed (Inspect)			Nov 30, 2023 8:21pm

[socket-security]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
rimraf	4.4.1	filesystem, environment	+6	2.48 MB	isaacs

[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.

Issue	Package	Version	Note	Source
Chronological version anomaly	minipass	4.2.8	Previous Chronological: minipass@5.0.0 (4/9/2023, 9:54:10 PM) Previous Semver: minipass@4.2.7 (4/9/2023, 9:24:19 PM)	@wordpress/env@5.12.0 via package.json rimraf@4.4.1 via packages/env/package.json
Major refactor	minipass	7.0.4	Change Percentage: 101.15 Current Line Count: 3142 Previous Line Count: 3142 Lines Changed: 6356	@wordpress/env@5.12.0 via package.json rimraf@4.4.1 via packages/env/package.json
Environment variable access	rimraf	4.4.1	Env Vars: TESTING_RIMRAF_NODE_VERSION Location: dist/cjs/src/use-native.js +1 more instances...	@wordpress/env@5.12.0 via package.json packages/env/package.json
Filesystem access	rimraf	4.4.1	Module: fs Location: dist/cjs/src/fs.js +5 more instances...	@wordpress/env@5.12.0 via package.json packages/env/package.json
Environment variable access	minimatch	8.0.4	Env Vars: MINIMATCH_TESTING_PLATFORM Location: dist/cjs/index.js +5 more instances...	@wordpress/env@5.12.0 via package.json rimraf@4.4.1 via packages/env/package.json
Filesystem access	path-scurry	1.10.1	Module: fs Location: dist/cjs/index.js +5 more instances...	@wordpress/env@5.12.0 via package.json rimraf@4.4.1 via packages/env/package.json
Unpublished package	lru-cache	10.1.0	Version: 10/1/2000, 12:00:00 AM	@wordpress/env@5.12.0 via package.json rimraf@4.4.1 via packages/env/package.json

Next steps

What is a chronological version anomaly?

Semantic versions published out of chronological order.

This could either indicate dependency confusion or a patched vulnerability.

What is a major refactor?

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Consider waiting before upgrading to see if any issues are discovered, or be prepared to scrutinize any bugs or subtle changes the major refactor may bring. Publishers my consider publishing beta versions of major refactors to limit disruption to parties interested in the new changes.

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

Package version was not found on the registry. It may exist on a different registry and need to be configured to pull from that registry.

Packages can be removed from the registry by manually un-publishing, a security issue removal, or may simply never have been published to the registry. Reliance on these packages will cause problem when they are not found.

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 rimraf@4.4.1
• @SocketSecurity ignore minimatch@8.0.4
• @SocketSecurity ignore lru-cache@10.1.0
• @SocketSecurity ignore minipass@4.2.8
• @SocketSecurity ignore minipass@7.0.4
• @SocketSecurity ignore path-scurry@1.10.1