[Snyk] Security upgrade gatsby from 4.25.7 to 5.14.2

[DevenGengan]

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

Snyk changed the following file(s):

• docs/package.json
• docs/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Cross-site Scripting (XSS) SNYK-JS-SERIALIZEJAVASCRIPT-6147607	626
	Cross-site Scripting (XSS) SNYK-JS-WEBPACK-7840298	616

---

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 Scripting (XSS)

[guardrails]

⚠️ We detected 1 security issue in this pull request:

Vulnerable Libraries (1)

Severity	Details
Critical	pkg:npm/[email protected] upgrade to: > 5.14.2

More info on how to fix Vulnerable Libraries in JavaScript.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[dryrunsecurity]

DryRun Security Summary

A Gatsby dependency was upgraded from version 4.25.7 to 5.14.2, involving a major version change that requires comprehensive testing to ensure system stability and security without identifying direct vulnerabilities.

Expand for full summary

Summary: A Gatsby dependency version upgrade from 4.25.7 to 5.14.2 was performed, involving a major version change with potential implications for system stability and security.

Security Findings:
• Potential Security Risks in Dependency Upgrade

• Major version upgrades can introduce unexpected security side effects
• Requires comprehensive testing to validate security integrity
• Potential for unintended breaking changes that might impact security configurations

No direct vulnerabilities were identified in the current patch, but careful validation is recommended.

View PR in the DryRun Dashboard.