[Snyk] Security upgrade sass from 1.58.3 to 1.79.0

[kingjay66]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncontrolled resource consumption SNYK-JS-BRACES-6838727	696

---

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

[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
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	package-lock.json package.json	🚫
Filesystem access	npm/@netlify/[email protected]	Module: fs Location: Package overview	package-lock.json package.json	🚫
Network access	npm/@netlify/[email protected]	Module: netlify Location: Package overview	package-lock.json package.json	🚫
Filesystem access	npm/@netlify/[email protected]	Module: fs Location: Package overview	package-lock.json package.json	🚫
Network access	npm/@netlify/[email protected]	Module: netlify-headers-parser Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/@netlify/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Network access	npm/@netlify/[email protected]	Module: netlify-redirect-parser Location: Package overview	package-lock.json package.json	🚫
Filesystem access	npm/@netlify/[email protected]	Module: fs Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/@netlify/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Network access	npm/@netlify/[email protected]	Module: globalThis["fetch"] Location: Package overview	package-lock.json package.json	🚫

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 is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

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.

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/@netlify/[email protected]
• @SocketSecurity ignore npm/@netlify/[email protected]
• @SocketSecurity ignore npm/@netlify/[email protected]