[Snyk] Security upgrade npm from 5.10.0 to 7.0.0

[tjenkinson]

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:
  • tests/cases/user/npm/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	718/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 6.5	Uncontrolled Resource Consumption ('Resource Exhaustion') SNYK-JS-TAR-6476909	Yes	Proof of Concept

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

Commit messages

Package name: npm

The new version differs by 250 commits.

• 3b4ba65 7.0.0
• bbfc75d chore: fix weird .gitignore thing that happened somehow
• 8a2d375 docs: changelog for v7.0.0
• 365f2e7 read-package-json@3.0.0
• fafb348 npm-package-arg@8.1.0
• 9306c68 libnpmfund@1.0.1
• 569cd64 libnpmfund@1.0.0
• ac9fde7 Integration code for @ npmcli/arborist@1.0.0
• 704b9cd @ npmcli/arborist@1.0.0
• 3955bb9 hosted-git-info@3.0.6
• da240ef fix: patch config.js to remove duplicate values
• 9ae45a8 init-package-json@2.0.0
• 41ab36d eslint@7.11.0
• c474a15 npm-registry-fetch@8.1.5
• efc6786 fix: make sure publishConfig is passed through
• 1e4e6e9 docs: v7 using npm config refresh
• 5c1c2da fix: init config aliases
• 5bc7eb2 docs: v7 npm-install refresh
• 1a35d87 7.0.0-rc.4
• 7a5a557 docs: changelog for v7.0.0-rc.4
• f0cf859 chore: dedupe deps
• 0273745 make-fetch-happen@8.0.10
• 7bd47ca @ npmcli/arborist@0.0.33
• 9320b8e only escape arguments, not the command name

See the full diff

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:

🦉 Uncontrolled Resource Consumption ('Resource Exhaustion')

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/del@7.1.0	Transitive: environment, filesystem	+39	805 kB	sindresorhus
npm/fancy-log@2.0.0	None	+1	15.6 kB	phated
npm/fs-extra@6.0.1	filesystem	0	150 kB	ryanzim
npm/gulp-concat@2.6.1	Transitive: environment, filesystem, unsafe	+15	1.04 MB	contra
npm/gulp-insert@0.5.0	Transitive: environment	+6	153 kB	rschmukler
npm/gulp-newer@1.4.0	filesystem Transitive: environment	+20	301 kB	tschaub
npm/gulp-rename@2.0.0	None	0	7.17 kB	contra
npm/gulp-sourcemaps@3.0.0	Transitive: environment, eval, filesystem	+40	3.71 MB	nmccready
npm/gulp@4.0.2	Transitive: environment, eval, filesystem, network, shell, unsafe	+190	3.49 MB	phated
npm/istanbul@0.4.5	filesystem, unsafe Transitive: environment, eval	+35	7.43 MB	gotwarlost
npm/merge2@1.4.1	None	0	8.9 kB	zensh
npm/minimist@1.2.8	None	0	54.5 kB	ljharb
npm/mkdirp@3.0.1	environment, filesystem	0	107 kB	isaacs
npm/mocha-fivemat-progress-reporter@0.1.0	filesystem	0	17.1 kB	danquirk
npm/mocha@10.3.0	environment, eval, filesystem	+43	4.29 MB	joshuakgoldberg
npm/node-fetch@2.7.0	network	0	162 kB	node-fetch-bot
npm/plugin-error@2.0.1	None	+2	38.6 kB	phated
npm/pretty-hrtime@1.0.3	None	0	6.35 kB	robrich
npm/prex@0.4.9	None	+2	474 kB	rbuckton
npm/q@1.5.1	None	0	123 kB	kriskowal
npm/remove-internal@2.9.3	Transitive: environment, filesystem, shell	+46	38.3 MB	ryancavanaugh
npm/simple-git@1.132.0	environment, filesystem, shell	0	123 kB	steveukx
npm/source-map-support@0.5.21	filesystem	+2	895 kB	linusu
npm/through2@4.0.2	None	+2	27.7 kB	rvagg
npm/travis-fold@0.1.2	environment	0	20 kB	macbre
npm/tslint@6.1.3	filesystem Transitive: environment, eval, shell	+35	36.3 MB	palantir

🚮 Removed packages: npm/npm@5.10.0

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
Install scripts	npm/fsevents@1.2.13	Install script: install Source: node install.js	package.json
Protestware/Troll package	npm/es5-ext@0.10.64	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	package.json
Install scripts	npm/es5-ext@0.10.64	Install script: postinstall Source: node -e "try{require('./_postinstall')}catch(e){}" || exit 0	package.json

View full report↗︎

Next steps

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

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package my come along with functionality unrelated to its primary purpose.

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/fsevents@1.2.13
• @SocketSecurity ignore npm/es5-ext@0.10.64