[Snyk] Security upgrade gatsby from 5.13.4 to 5.14.0

[snyk-io]

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

Snyk changed the following file(s):

• gatsby-contentful/package.json
• gatsby-contentful/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795	159
	Path Traversal SNYK-JS-WEBPACKDEVMIDDLEWARE-6476555	158
	Cross-site Request Forgery (CSRF) SNYK-JS-AXIOS-6032459	155
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	141
	Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860	111
	Denial of Service (DoS) SNYK-JS-MSGPACKR-6140431	111
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AXIOS-6124857	67
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106	67
	Regular Expression Denial of Service (ReDoS) SNYK-JS-HTTPCACHESEMANTICS-3248783	63

---

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:

🦉 Cross-site Request Forgery (CSRF)
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Path Traversal

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@stackbit/cms-contentful@0.4.50	environment Transitive: eval, filesystem, network, shell, unsafe	+575	584 MB	stackbit-admin
npm/@stackbit/types@0.11.14	None	0	386 kB	stackbit-admin
npm/@types/node@20.11.16	None	0	3.99 MB	types
npm/@types/react@18.2.53	None	+3	1.64 MB	types
npm/contentful-export@7.19.70	filesystem Transitive: environment, eval, network, unsafe	+83	22.1 MB	contentful-ecosystem
npm/contentful-import@9.0.8	filesystem Transitive: environment, eval, network, unsafe	+179	37.4 MB	contentful-ecosystem
npm/eslint-config-next@13.4.4	unsafe Transitive: environment, eval, filesystem	+112	14.3 MB	vercel-release-bot
npm/eslint@8.48.0	environment, filesystem Transitive: eval, shell, unsafe	+63	9.77 MB	eslintbot
npm/markdown-to-jsx@7.2.1	None	0	404 kB	probablyup
npm/next@13.5.6	environment, filesystem, network, shell, unsafe	+16	1.11 GB	vercel-release-bot

🚮 Removed packages: npm/@stackbit/cms-contentful@0.4.48, npm/@stackbit/types@0.11.12, npm/@types/node@20.12.7, npm/@types/react-dom@18.2.25, npm/@types/react@18.2.79, npm/contentful-import@8.5.45

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
Protestware or potentially unwanted behavior	npm/es5-ext@0.10.64	Note: The script attempts to run a local post-install script, which could potentially contain malicious code. The error handling suggests that it is designed to fail silently, which is a common tactic in malicious scripts.	i18n-nextjs-contentful/package-lock.json i18n-nextjs-contentful/package.json	⚠︎

View full report↗︎

Next steps

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 may 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/es5-ext@0.10.64