[Snyk] Fix for 31 vulnerabilities

[hashim2266]

Snyk has created this PR to fix 31 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• landing/package.json
• landing/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Code Injection SNYK-JS-LODASH-1040724	248
	Arbitrary Code Injection SNYK-JS-SERIALIZEJAVASCRIPT-570062	227
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-15309438	169
	Inefficient Algorithmic Complexity SNYK-JS-MINIMATCH-15353389	169
	Prototype Poisoning SNYK-JS-QS-3153490	161
	Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795	160
	Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908	159
	Excessive Platform Resource Consumption within a Loop SNYK-JS-BRACES-6838727	159
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	159
	Denial of Service (DoS) SNYK-JS-DECODEURICOMPONENT-3149970	159
	Prototype Pollution SNYK-JS-Y18N-1021887	150
	Cross-site Scripting (XSS) SNYK-JS-WEBPACK-7840298	146
	Prototype Pollution SNYK-JS-LOADERUTILS-3043105	144
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BABELRUNTIME-10044504	140
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	131
	Infinite loop SNYK-JS-BRACEEXPANSION-15789759	124
	Allocation of Resources Without Limits or Throttling SNYK-JS-SERIALIZEJAVASCRIPT-15809196	124
	Prototype Pollution SNYK-JS-UNSETVALUE-2400660	115
	Cross-site Scripting (XSS) SNYK-JS-POSTCSS-16189065	108
	Information Exposure SNYK-JS-NODEFETCH-2342118	104
	Cross-site Scripting (XSS) SNYK-JS-SERIALIZEJAVASCRIPT-6147607	102
	Regular Expression Denial of Service (ReDoS) SNYK-JS-GLOBPARENT-1016905	63
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-1018905	63
	Regular Expression Denial of Service (ReDoS) SNYK-JS-POSTCSS-1090595	63
	Regular Expression Denial of Service (ReDoS) SNYK-JS-POSTCSS-1255640	63
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BRACEEXPANSION-9789073	57
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LOADERUTILS-3042992	47
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LOADERUTILS-3105943	46
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	45
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-3050818	45
	Improper Input Validation SNYK-JS-POSTCSS-5926692	45

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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)
🦉 Prototype Pollution
🦉 Code Injection
🦉 More lessons are available in Snyk Learn

[hashim2266]

This release includes two major version upgrades, tailwindcss and autoprefixer, which introduce significant breaking changes. The other upgrades are minor or patch versions and are considered low-risk.

Highlights

• tailwindcss 1.1.2 → 2.0.0 (HIGH RISK)
  This is a major upgrade with several breaking changes that require developer action. Key changes include:

  • Environment: Support for IE11 and Node.js versions below 12.13.0 has been dropped.
  • Dependencies: Tailwind CSS v2.0 now requires PostCSS 8 and autoprefixer v10 as peer dependencies.
  • Plugin System: The @tailwindcss/custom-forms plugin is no longer compatible and has been replaced by the new @tailwindcss/forms plugin.
  • Class Changes: Some utility classes have been renamed or removed. For example, shadow-outline is replaced by ring utilities, and font-weight classes like font-hairline have been renamed.
  • Behavioral Changes: Font-size utilities now include a default line-height, which may affect your typography.

  Recommendation: Developers must follow the official Tailwind CSS v2.0 upgrade guide to update their configuration, dependencies, and class names. Expect to spend about 30 minutes on the migration.

• autoprefixer 9.6.4 → 10.0.0 (MEDIUM RISK)
  This major version upgrade requires changes to your build environment.

  • Environment: Support for Node.js versions 6.x, 8.x, and 11.x has been removed.
  • Dependencies: autoprefixer@10 requires PostCSS 8. This is a necessary part of the tailwindcss upgrade.

Other Upgrades

• Low Risk Upgrades: The following are patch or minor updates that include bug fixes and security patches with no expected breaking changes:
  • next 10.0.3 → 10.0.6: Contains bug fixes. No breaking changes are documented for this range.
  • lodash 4.17.20 → 4.17.21: A security release addressing a prototype pollution vulnerability.
  • qs 6.9.1 → 6.9.7: Includes security and bug fixes.
  • @brunolemos/devhub-core 0.102.1-rc.0 → 0.103.0: A minor update, likely containing features and bug fixes. No detailed changelog was found.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​zeit/​next-css@​1.0.1
	@​types/​styled-jsx@​2.2.8
	next@​10.0.6
	@​types/​classnames@​2.2.11
	eslint-config-nextjs@​1.0.7
	node-fetch@​2.6.1
	@​types/​qs@​6.9.0 ⏵ 6.9.5			+1
	lodash@​4.17.21
	@​types/​stripe-v3@​3.1.9
	react@​17.0.1
	isomorphic-unfetch@​3.1.0
	@​types/​node@​12.19.8 ⏵ 14.14.11	+1		+1	-2
	next-transpile-modules@​6.0.0
	typescript@​4.3.4
	now@​21.0.1
	shx@​0.3.3
	classnames@​2.2.6
	ts-node@​9.1.1
	react-stripe-elements@​5.0.1
	tailwindcss@​2.0.0
	autoprefixer@​9.8.6 ⏵ 10.0.0
	react-dom@​17.0.1
	prettier@​2.3.1
	qs@​6.7.0 ⏵ 6.9.7		+16

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: Prototype Pollution in npm minimist CVE: GHSA-xvch-5gv4-984h Prototype Pollution in minimist (CRITICAL) Affected versions: >= 1.0.0 < 1.2.6; < 0.2.4 Patched version: 1.2.6 From: ? → npm/now@21.0.1 → npm/next@10.0.6 → npm/@zeit/next-css@1.0.1 → npm/shx@0.3.3 → npm/minimist@1.2.5 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/minimist@1.2.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: npm pbkdf2 returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algos CVE: GHSA-h7cp-r72f-jxh6 pbkdf2 returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algos (CRITICAL) Affected versions: >= 3.0.10 < 3.1.3 Patched version: 3.1.3 From: ? → npm/next@10.0.6 → npm/pbkdf2@3.1.1 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/pbkdf2@3.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: npm pbkdf2 silently disregards Uint8Array input, returning static keys CVE: GHSA-v62p-rq8g-8h59 pbkdf2 silently disregards Uint8Array input, returning static keys (CRITICAL) Affected versions: >= 1.0.0 < 3.1.3 Patched version: 3.1.3 From: ? → npm/next@10.0.6 → npm/pbkdf2@3.1.1 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/pbkdf2@3.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: npm sha.js is missing type checks leading to hash rewind and passing on crafted data CVE: GHSA-95m3-7q98-8xr5 sha.js is missing type checks leading to hash rewind and passing on crafted data (CRITICAL) Affected versions: < 2.4.12 Patched version: 2.4.12 From: ? → npm/next@10.0.6 → npm/sha.js@2.4.11 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/sha.js@2.4.11. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: Improper Neutralization of Special Elements used in a Command in Shell-quote CVE: GHSA-g4rg-993r-mgx7 Improper Neutralization of Special Elements used in a Command in Shell-quote (CRITICAL) Affected versions: >= 1.6.3 < 1.7.3 Patched version: 1.7.3 From: ? → npm/next@10.0.6 → npm/shell-quote@1.7.2 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/shell-quote@1.7.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report