[Snyk] Security upgrade webpack-cli from 2.1.5 to 4.0.0

[naiba4]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• demo/webpack/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	828

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

[changeset-bot]

⚠️ No Changeset found

Latest commit: e0f3516

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, filesystem Transitive: shell, unsafe	+40	1.07 MB	evilebottnawi

🚮 Removed packages: 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	CI
Unmaintained	npm/[email protected]	Last Publish: 11/8/2016, 4:05:13 AM	Source	🚫
Unmaintained	npm/[email protected]	Last Publish: 11/22/2018, 12:00:24 AM	demo/webpack/package.json	🚫
Unmaintained	npm/[email protected]	Last Publish: 4/16/2019, 12:06:42 AM	demo/webpack/package.json	🚫
Environment variable access	npm/@webpack-cli/[email protected]	Env Vars: WEBPACK_PACKAGE Location: Package overview	demo/webpack/package.json	🚫
Environment variable access	npm/@webpack-cli/[email protected]	Env Vars: WEBPACK_DEV_SERVER_PACKAGE Location: Package overview	demo/webpack/package.json	🚫
Dynamic require	npm/@webpack-cli/[email protected]	Location: Package overview	demo/webpack/package.json	🚫
Dynamic require	npm/@webpack-cli/[email protected]	Location: Package overview	demo/webpack/package.json	🚫
Dynamic require	npm/@webpack-cli/[email protected]	Location: Package overview	demo/webpack/package.json	🚫
Dynamic require	npm/[email protected]	Location: Package overview	demo/webpack/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: WEBPACK_PACKAGE Location: Package overview	demo/webpack/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: WEBPACK_DEV_SERVER_PACKAGE Location: Package overview	demo/webpack/package.json	🚫
Dynamic require	npm/[email protected]	Location: Package overview	demo/webpack/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: WEBPACK_CLI_FORCE_LOAD_ESM_CONFIG Location: Package overview	demo/webpack/package.json	🚫
Dynamic require	npm/[email protected]	Location: Package overview	demo/webpack/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: WEBPACK_CLI_HELP_WIDTH Location: Package overview	demo/webpack/package.json	🚫
Environment variable access	npm/[email protected]	Location: Package overview	demo/webpack/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	demo/webpack/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	demo/webpack/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	demo/webpack/package.json	🚫
Unmaintained	npm/[email protected]	Last Publish: 6/6/2016, 1:13:09 AM	Source	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	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 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 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.

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud