Bump vite-plugin-solid from 2.11.12 to 2.11.13

[dependabot]

Bumps vite-plugin-solid from 2.11.12 to 2.11.13.

Release notes

Sourced from vite-plugin-solid's releases.

vite-plugin-solid@2.11.13

Patch Changes

• 35ce381: Use per-environment Vite plugin hook APIs while retaining compatibility with Vite 3 through 5.

Changelog

Sourced from vite-plugin-solid's changelog.

2.11.13

Patch Changes

• 35ce381: Use per-environment Vite plugin hook APIs while retaining compatibility with Vite 3 through 5.

Commits

• 7dd3a9a Version Packages (#276)
• 35ce381 [main] Vite 9 forward-compat (#273)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​vite-plugin-solid@​2.11.12 ⏵ 2.11.13				+10

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Dynamic code execution: npm @babel/traverse Eval Type: Function Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/traverse@7.29.7 ℹ Read more on: This package | This alert | What is dynamic code execution? 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: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/traverse@7.29.7. 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.
Block		Dynamic code execution: npm babel-plugin-jsx-dom-expressions Eval Type: Function Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/babel-plugin-jsx-dom-expressions@0.40.7 ℹ Read more on: This package | This alert | What is dynamic code execution? 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: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/babel-plugin-jsx-dom-expressions@0.40.7. 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.
Block		Environment variable access: npm @babel/code-frame reads FORCE_COLOR Env Vars: FORCE_COLOR Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/code-frame@7.29.7 ℹ Read more on: This package | This alert | What is environment variable access? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/code-frame@7.29.7. 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.
Block		Debug access: npm @babel/core in module module Module: module Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/core@7.29.7 ℹ Read more on: This package | This alert | What is debug access? 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: Removing the use of debug will reduce the risk of any reflection and dynamic code execution. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/core@7.29.7. 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.
Block		Debug access: npm @babel/core in module v8 Module: v8 Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/core@7.29.7 ℹ Read more on: This package | This alert | What is debug access? 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: Removing the use of debug will reduce the risk of any reflection and dynamic code execution. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/core@7.29.7. 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.
Block		Environment variable access: npm @babel/core reads BABEL_SHOW_CONFIG_FOR Env Vars: BABEL_SHOW_CONFIG_FOR Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/core@7.29.7 ℹ Read more on: This package | This alert | What is environment variable access? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/core@7.29.7. 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.
Block		Environment variable access: npm @babel/core reads BABEL_ENV Env Vars: BABEL_ENV Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/core@7.29.7 ℹ Read more on: This package | This alert | What is environment variable access? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/core@7.29.7. 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.
Block		Environment variable access: npm @babel/core reads NODE_ENV Env Vars: NODE_ENV Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/core@7.29.7 ℹ Read more on: This package | This alert | What is environment variable access? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/core@7.29.7. 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.
Block		Filesystem access: npm @babel/core with module fs Module: fs Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/core@7.29.7 ℹ Read more on: This package | This alert | What is filesystem access? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/core@7.29.7. 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.
Block		Embedded URLs or IPs: npm @babel/core URLs: http://babeljs.io/docs/plugins/external-helpers/, http://babeljs.io/docs/plugins/transform-react-jsx/, http://babeljs.io/docs/plugins/#modules, http://babeljs.io/docs/plugins/preset-react/, http://babeljs.io/docs/plugins/#presets, https://babeljs.io/docs/en/babel-core/#options, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-async-do-expressions, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-decimal, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-decorators, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-decorators, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-do-expressions, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-do-expressions, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-export-default-from, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-export-default-from, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-flow, https://github.com/babel/babel/tree/main/packages/babel-preset-flow, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-function-bind, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-function-bind, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-function-sent, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-function-sent, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-jsx, https://github.com/babel/babel/tree/main/packages/babel-preset-react, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-pipeline-operator, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-pipeline-operator, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-record-and-tuple, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-throw-expressions, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-throw-expressions, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-typescript, https://github.com/babel/babel/tree/main/packages/babel-preset-typescript, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-async-generators, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-async-generator-functions, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-class-properties, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-class-properties, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-private-methods, https://github.com/babel/babel/tree/HEAD/packages/babel-plugin-syntax-class-static-block, https://github.com/babel/babel/tree/HEAD/packages/babel-plugin-transform-class-static-block, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-dynamic-import, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-export-namespace-from, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-export-namespace-from, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-import-assertions, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-import-attributes, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-import-meta, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-logical-assignment-operators, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-logical-assignment-operators, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-module-string-names, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-numeric-separator, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-numeric-separator, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-nullish-coalescing-operator, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-nullish-coalescing-opearator, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-object-rest-spread, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-object-rest-spread, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-optional-catch-binding, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-optional-catch-binding, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-optional-chaining, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-optional-chaining, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-private-property-in-object, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-private-property-in-object, https://github.com/babel/babel/blob/main/packages/babel-plugin-syntax-unicode-sets-regex/README.md, https://github.com/babel/babel/blob/main/packages/babel-plugin-proposalunicode-sets-regex/README.md, https://babeljs.io/docs/configuration#print-effective-configs, https://babeljs.io/docs/en/options#filename Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/core@7.29.7 ℹ Read more on: This package | This alert | What are URL strings? 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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/core@7.29.7. 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.
Block		Environment variable access: npm @babel/helper-compilation-targets reads BROWSERSLIST Env Vars: BROWSERSLIST Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/helper-compilation-targets@7.29.7 ℹ Read more on: This package | This alert | What is environment variable access? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/helper-compilation-targets@7.29.7. 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.
Block		Environment variable access: npm @babel/helper-compilation-targets reads BROWSERSLIST_CONFIG Env Vars: BROWSERSLIST_CONFIG Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/helper-compilation-targets@7.29.7 ℹ Read more on: This package | This alert | What is environment variable access? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/helper-compilation-targets@7.29.7. 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.
Block		Dynamic module loading: npm @babel/helper-module-imports Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/helper-module-imports@7.18.6 ℹ Read more on: This package | This alert | What is dynamic require? 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: Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/helper-module-imports@7.18.6. 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.
Block		Dynamic module loading: npm @babel/helper-module-imports Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/helper-module-imports@7.29.7 ℹ Read more on: This package | This alert | What is dynamic require? 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: Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/helper-module-imports@7.29.7. 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.
Block		Embedded URLs or IPs: npm @babel/helpers URLs: body.0.id, body.1.id, body.0.declarations.0.id, body.2.id, body.3.id, body.4.id, body.5.id, body.6.id, body.7.id, https://github.com/babel/babel/blob/main/packages/babel-helpers/LICENSE, body.8.id, body.9.id, body.10.id, body.11.id, body.12.id, body.13.id, body.1.declarations.0.id Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/helpers@7.29.7 ℹ Read more on: This package | This alert | What are URL strings? 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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/helpers@7.29.7. 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.
Block		Embedded URLs or IPs: npm @babel/traverse with tag.property URLs: tag.property Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/traverse@7.29.7 ℹ Read more on: This package | This alert | What are URL strings? 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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/traverse@7.29.7. 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.
Block		Environment variable access: npm @babel/types reads BABEL_TYPES_8_BREAKING Env Vars: BABEL_TYPES_8_BREAKING Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/@babel/types@7.29.7 ℹ Read more on: This package | This alert | What is environment variable access? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/types@7.29.7. 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.
Block		Embedded URLs or IPs: npm babel-plugin-jsx-dom-expressions URLs: http://www.w3.org/1999/xlink, http://www.w3.org/XML/1998/namespace Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/babel-plugin-jsx-dom-expressions@0.40.7 ℹ Read more on: This package | This alert | What are URL strings? 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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/babel-plugin-jsx-dom-expressions@0.40.7. 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.
Block		Publisher changed: npm convert-source-map is now published by phated instead of thlorenz New Author: phated Previous Author: thlorenz From: ? → npm/vite-plugin-solid@2.11.13 → npm/convert-source-map@2.0.0 ℹ Read more on: This package | This alert | What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/convert-source-map@2.0.0. 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.
Block		Embedded URLs or IPs: npm convert-source-map URLs: https://github.com/thlorenz/convert-source-map#upgrading Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/convert-source-map@2.0.0 ℹ Read more on: This package | This alert | What are URL strings? 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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/convert-source-map@2.0.0. 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.
Block		Environment variable access: npm debug reads DEBUG Env Vars: DEBUG Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/debug@4.4.3 ℹ Read more on: This package | This alert | What is environment variable access? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/debug@4.4.3. 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.
Block		Environment variable access: npm debug Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/debug@4.4.3 ℹ Read more on: This package | This alert | What is environment variable access? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/debug@4.4.3. 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.
Block		Unmaintained: npm gensync was last published 6 years ago Last Publish: 10/27/2020, 8:43:40 PM From: ? → npm/vite-plugin-solid@2.11.13 → npm/gensync@1.0.0-beta.2 ℹ Read more on: This package | This alert | What are unmaintained packages? 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: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/gensync@1.0.0-beta.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.
Block		Minified code present: npm html-entities with 98.0% likelihood Confidence: 0.98 Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/html-entities@2.3.3 ℹ Read more on: This package | This alert | What's wrong with minified code? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/html-entities@2.3.3. 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.
Block		Embedded URLs or IPs: npm parse5 URLs: http://www.ibm.com/data/dtd/v11/ibmxhtml1-transitional.dtd, http://www.w3.org/1999/xhtml, http://www.w3.org/1998/Math/MathML, http://www.w3.org/2000/svg, http://www.w3.org/1999/xlink, http://www.w3.org/XML/1998/namespace, http://www.w3.org/2000/xmlns/ Location: Package overview From: ? → npm/vite-plugin-solid@2.11.13 → npm/parse5@7.3.0 ℹ Read more on: This package | This alert | What are URL strings? 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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/parse5@7.3.0. 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

[dependabot]

Dependabot can't parse your package.json. Because of this, Dependabot cannot update this pull request.