[Snyk] Security upgrade svelte from 3.59.2 to 4.2.19

[naiba4]

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

Snyk changed the following file(s):

• packages/kit/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Cross-site Scripting (XSS) SNYK-JS-SVELTE-7856103	658

---

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)

[changeset-bot]

⚠️ No Changeset found

Latest commit: db3e984

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@types/node@12.20.55	None	0	760 kB	types
npm/magic-string@0.30.11	None	0	464 kB	antfu

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
Network access	npm/node-fetch@2.7.0	Module: http Location: Package overview	package.json pnpm-lock.yaml	🚫
Network access	npm/node-fetch@2.7.0	Module: https Location: Package overview	package.json pnpm-lock.yaml	🚫
Network access	npm/node-fetch@2.7.0	Module: globalThis["fetch"] Location: Package overview	package.json pnpm-lock.yaml	🚫
Filesystem access	npm/jsonfile@4.0.0	Module: fs Location: Package overview	package.json pnpm-lock.yaml	🚫
Filesystem access	npm/resolve@1.22.8	Module: fs Location: Package overview	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Environment variable access	npm/resolve@1.22.8	Env Vars: HOME Location: Package overview	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Environment variable access	npm/resolve@1.22.8	Env Vars: LOGNAME Location: Package overview	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Environment variable access	npm/resolve@1.22.8	Env Vars: USER Location: Package overview	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Environment variable access	npm/resolve@1.22.8	Env Vars: LNAME Location: Package overview	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Environment variable access	npm/resolve@1.22.8	Env Vars: USERNAME Location: Package overview	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Environment variable access	npm/resolve@1.22.8	Env Vars: USERPROFILE Location: Package overview	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Environment variable access	npm/resolve@1.22.8	Env Vars: HOMEDRIVE Location: Package overview	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Environment variable access	npm/resolve@1.22.8	Env Vars: HOMEPATH Location: Package overview	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Unmaintained	npm/commondir@1.0.1	Last Publish: 3/14/2015, 12:15:01 AM	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Floating dependency	npm/is-reference@1.2.1	Location: Package overview	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json packages/adapter-static/package.json packages/adapter-static/test/apps/prerendered/package.json packages/adapter-static/test/apps/spa/package.json packages/create-svelte/package.json packages/create-svelte/templates/default/package.json pnpm-lock.yaml	🚫
Unmaintained	npm/is-module@1.0.0	Last Publish: 4/1/2014, 12:58:29 AM	package.json packages/adapter-netlify/package.json packages/adapter-node/package.json pnpm-lock.yaml	🚫
Network access	npm/@changesets/get-github-info@0.5.2	Module: globalThis["fetch"] Location: Package overview	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/@changesets/get-github-info@0.5.2	Env Vars: GITHUB_TOKEN Location: Package overview	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/@changesets/get-github-info@0.5.2	Env Vars: NODE_ENV Location: Package overview	package.json pnpm-lock.yaml	🚫
Filesystem access	npm/dotenv@16.4.5	Module: fs Location: Package overview	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/dotenv@16.4.5	Env Vars: DOTENV_KEY Location: Package overview	package.json pnpm-lock.yaml	🚫
Environment variable access	npm/dotenv@16.4.5	Location: Package overview	package.json pnpm-lock.yaml	🚫

View full report↗︎

Next steps

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 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 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 are unmaintained packages?

Package has not been updated in more than 5 years and may be unmaintained. Problems with the package may go unaddressed.

Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

What are wildcard dependencies?

Package has a dependency with a floating version range. This can cause issues if the dependency publishes a new major version.

Packages should specify properly semver ranges to avoid version conflicts.

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/node-fetch@2.7.0
• @SocketSecurity ignore npm/jsonfile@4.0.0
• @SocketSecurity ignore npm/resolve@1.22.8
• @SocketSecurity ignore npm/commondir@1.0.1
• @SocketSecurity ignore npm/is-reference@1.2.1
• @SocketSecurity ignore npm/is-module@1.0.0
• @SocketSecurity ignore npm/@changesets/get-github-info@0.5.2
• @SocketSecurity ignore npm/dotenv@16.4.5