[Snyk] Security upgrade bootstrap from 4.6.2 to 5.0.0

[Abuchtela]

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


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

Snyk changed the following file(s):

• examples/with-react-bootstrap/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Cross-site Scripting (XSS) SNYK-JS-BOOTSTRAP-7444580	204
	Cross-site Scripting SNYK-JS-BOOTSTRAP-7444617	204

---

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)

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@actions/core@1.9.0	environment, filesystem Transitive: network	+2	206 kB	thboop
npm/@actions/github@5.0.3	environment, filesystem Transitive: network	+22	4.91 MB	thboop
npm/@vercel/ncc@0.34.0	filesystem, unsafe	0	15.5 MB	styfle
npm/classnames@2.5.1	None	0	23.6 kB	jedwatson
npm/date-fns@2.30.0	None	0	6.69 MB	kossnocorp
npm/empty-npm-package@1.0.0	None	0	328 B	mohit-divcraft

🚮 Removed packages: npm/@apollo/client@3.10.8, npm/@apollo/server@4.10.4, npm/@as-integrations/next@1.3.0, npm/@auth0/nextjs-auth0@1.9.3, npm/@babel/types@7.18.0, npm/@faker-js/faker@7.6.0, npm/@formatjs/intl-localematcher@0.2.32, npm/@graphql-tools/schema@9.0.19, npm/@hapi/iron@6.0.0, npm/@mdx-js/react@2.3.0, npm/@next/bundle-analyzer@12.3.4, npm/@next/font@13.1.1, npm/@next/mdx@13.5.6, npm/@stytch/stytch-react@3.0.7, npm/@szmarczak/http-timer@5.0.1, npm/@types/cors@2.8.17, npm/@types/negotiator@0.6.1, npm/@types/node@18.11.18, npm/@types/node@18.19.39, npm/@types/react-dom@18.0.10, npm/@types/react-dom@18.3.0, npm/@types/react@17.0.37, npm/@types/react@18.0.26, npm/@types/react@18.3.3, npm/@types/uuid@8.3.4, npm/asciichart@1.5.25, npm/async-sema@3.1.1, npm/cross-env@7.0.3, npm/dotenv@10.0.0, npm/downsample-lttb@0.0.1, npm/eslint-config-next@13.1.1, npm/eslint@8.31.0, npm/fs-extra@10.0.0, npm/fs-extra@8.1.0, npm/graphql-yoga@3.9.1, npm/graphql@16.6.0, npm/listr2@5.0.5, npm/next-iron-session@4.2.0, npm/next@12.0.7, npm/next@13.1.1, npm/next@14.2.5, npm/p-queue@7.3.0, npm/prettier@1.19.1, npm/pretty-ms@5.1.0, npm/pretty-ms@7.0.1, npm/react-dom@17.0.2, npm/recursive-copy@2.0.11, npm/semver@7.3.4, npm/serve@13.0.4, npm/stytch@3.13.1, npm/typescript@4.9.4, npm/uuid@8.1.0, npm/webpack-stats-plugin@1.1.3

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
Install scripts	npm/preact@8.5.3	Install script: postinstall Source: node -e "console.log('\u001b[35m\u001b[1mLove Preact? You can now donate to our open collective:\u001b[22m\u001b[39m\n > \u001b[34mhttps://opencollective.com/preact/donate\u001b[0m')"	orphan: npm/preact@8.5.3	🚫

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.

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/preact@8.5.3