[Snyk] Security upgrade tailwindcss from 3.3.2 to 3.4.15

[naiba4]

Snyk has created this PR to fix 4 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
	Uncontrolled resource consumption SNYK-JS-BRACES-6838727	169
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	141
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	124
	Improper Input Validation SNYK-JS-POSTCSS-5926692	45

---

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:

🦉 Uncontrolled resource consumption
🦉 Improper Input Validation

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[changeset-bot]

⚠️ No Changeset found

Latest commit: d593def

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[guardrails]

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

Vulnerable Libraries (1)

Severity	Details
High	pkg:npm/[email protected] upgrade to: > 3.4.15

More info on how to fix Vulnerable Libraries in JavaScript.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, filesystem	+3	372 kB	ai

🚮 Removed packages: npm/[email protected], npm/[email protected]

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	CI
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	🚫
Minified code	npm/[email protected]	Confidence: 1.00 Location: Package overview	🚫
High entropy strings	npm/[email protected]	Location: Package overview	🚫
Debug access	npm/[email protected]	Module: module Location: Package overview	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	🚫
Debug access	npm/[email protected]	Module: v8 Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: JITI_DEBUG Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: JITI_CACHE Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: JITI_ESM_RESOLVE Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: JITI_REQUIRE_CACHE Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: JITI_SOURCE_MAPS Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: JITI_ALIAS Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: JITI_TRANSFORM_MODULES Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: JITI_NATIVE_MODULES Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: JITI_EXPERIMENTAL_BUN Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: TMPDIR Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: JITI_RESPECT_TMPDIR_ENV Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: TMPDIR Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: TMPDIR Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: TMPDIR Location: Package overview	🚫
Environment variable access	npm/[email protected]	Location: Package overview	🚫
Environment variable access	npm/[email protected]	Env Vars: MINIMATCH_TESTING_PLATFORM Location: Package overview	🚫
Environment variable access	npm/[email protected]	Location: Package overview	🚫
Shell access	npm/[email protected]	Module: child_process Location: Package overview	🚫

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What's wrong with minified code?

This package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.

In many cases minified code is harmless, however minified code can be used to hide a supply chain attack. Consider not shipping minified code on npm.

What are high entropy strings?

Contains high entropy strings. This could be a sign of encrypted data, leaked secrets or obfuscated code.

Please inspect these strings to check if these strings are benign. Maintainers should clarify the purpose and existence of high entropy strings if there is a legitimate purpose.

What is debug access?

Uses debug, reflection and dynamic code execution features.

Removing the use of debug will reduce the risk of any reflection and dynamic code execution.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]