| Block |
 |
Network access: npm @vscode/l10n in module globalThis["fetch"]
Module: globalThis["fetch"]
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/@vscode/l10n@0.0.18
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@vscode/l10n@0.0.18. 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 |
|
Network access: npm request-light in module http
Module: http
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/request-light@0.5.8
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/request-light@0.5.8. 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 |
|
Network access: npm request-light in module https
Module: https
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/request-light@0.5.8
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/request-light@0.5.8. 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 |
|
Network access: npm request-light in module net
Module: net
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/request-light@0.5.8
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/request-light@0.5.8. 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 |
|
Network access: npm request-light in module tls
Module: tls
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/request-light@0.5.8
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/request-light@0.5.8. 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 |
|
Network access: npm request-light in module http
Module: http
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/request-light@0.7.0
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/request-light@0.7.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 |
|
Network access: npm request-light in module https
Module: https
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/request-light@0.7.0
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/request-light@0.7.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 |
|
Network access: npm request-light in module net
Module: net
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/request-light@0.7.0
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/request-light@0.7.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 |
|
Network access: npm request-light in module tls
Module: tls
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/request-light@0.7.0
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/request-light@0.7.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 |
|
Network access: npm vscode-css-languageservice in module globalThis["fetch"]
Module: globalThis["fetch"]
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/vscode-css-languageservice@6.3.10
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/vscode-css-languageservice@6.3.10. 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 |
|
Network access: npm vscode-jsonrpc in module net
Module: net
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/vscode-jsonrpc@8.2.0
ℹ Read more on: This package | This alert | What is network 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/vscode-jsonrpc@8.2.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 |
|
System shell access: npm vscode-languageserver in module child_process
Module: child_process
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/vscode-languageserver@9.0.1
ℹ Read more on: This package | This alert | What is shell 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 avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/vscode-languageserver@9.0.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.
|
| Block |
 |
Dynamic module loading: npm @astrojs/language-server
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/@astrojs/language-server@2.16.13
ℹ 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/@astrojs/language-server@2.16.13. 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 @astrojs/language-server with module node:fs
Module: node:fs
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/@astrojs/language-server@2.16.13
ℹ 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/@astrojs/language-server@2.16.13. 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 @astrojs/language-server
URLs: https://docs.astro.build/en/guides/typescript/#component-props, https://docs.astro.build/en/reference/routing-reference/#getstaticpaths, https://docs.astro.build/en/guides/on-demand-rendering/#enabling-on-demand-rendering, https://docs.astro.build/en/reference/routing-reference/#prerender, https://docs.astro.build/en/reference/directives-reference/#classlist, https://docs.astro.build/en/basics/astro-components/#slots, https://docs.astro.build/en/basics/astro-components/#named-slots, https://docs.astro.build/en/reference/directives-reference/#definevars, https://docs.astro.build/en/core-concepts/astro-components/#using-hoisted-scripts, https://docs.astro.build/en/reference/directives-reference/#isinline, https://docs.astro.build/en/guides/view-transitions/#data-astro-rerun, https://docs.astro.build/en/reference/directives-reference/#isglobal, https://docs.astro.build/en/reference/directives-reference/#sethtml, https://docs.astro.build/en/reference/directives-reference/#settext, https://docs.astro.build/en/reference/directives-reference/#israw, https://docs.astro.build/en/guides/view-transitions/#transition-directives, https://docs.astro.build/en/reference/directives-reference/#clientload, https://docs.astro.build/en/reference/directives-reference/#clientidle, https://docs.astro.build/en/reference/directives-reference/#clientvisible, https://docs.astro.build/en/reference/directives-reference/#clientmedia, https://docs.astro.build/en/reference/directives-reference/#clientonly, https://github.com/withastro/astro/issues, https://github.com/withastro/roadmap/discussions/1321
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/@astrojs/language-server@2.16.13
ℹ 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/@astrojs/language-server@2.16.13. 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 @emmetio/css-parser is now published by serge.che instead of emmetio
New Author: serge.che
Previous Author: emmetio
From: ? → npm/@astrojs/check@0.9.10 → npm/@emmetio/css-parser@0.4.1
ℹ 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/@emmetio/css-parser@0.4.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.
|
| Block |
|
Unmaintained: npm @emmetio/html-matcher was last published 6 years ago
Last Publish: 5/27/2020, 3:50:49 PM
From: ? → npm/@astrojs/check@0.9.10 → npm/@emmetio/html-matcher@1.3.0
ℹ 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/@emmetio/html-matcher@1.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.
|
| Block |
|
Unmaintained: npm @emmetio/stream-reader-utils was last published 9 years ago
Last Publish: 3/22/2017, 10:56:28 PM
From: ? → npm/@astrojs/check@0.9.10 → npm/@emmetio/stream-reader-utils@0.1.0
ℹ 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/@emmetio/stream-reader-utils@0.1.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 |
|
Unmaintained: npm @emmetio/stream-reader was last published 9 years ago
Last Publish: 4/25/2017, 9:23:13 PM
From: ? → npm/@astrojs/check@0.9.10 → npm/@emmetio/stream-reader@2.2.0
ℹ 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/@emmetio/stream-reader@2.2.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 |
|
Filesystem access: npm @volar/kit with module fs
Module: fs
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/@volar/kit@2.4.28
ℹ 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/@volar/kit@2.4.28. 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 @vscode/emmet-helper is now published by microsoft1es instead of vscode-bot
New Author: microsoft1es
Previous Author: vscode-bot
From: ? → npm/@astrojs/check@0.9.10 → npm/@vscode/emmet-helper@2.11.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/@vscode/emmet-helper@2.11.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 @vscode/emmet-helper
URLs: https://code.visualstudio.com/docs/editor/emmet#_emmet-configuration, https://code.visualstudio.com/docs/editor/emmet#_using-custom-emmet-snippets
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/@vscode/emmet-helper@2.11.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/@vscode/emmet-helper@2.11.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 |
|
Filesystem access: npm @vscode/l10n with module fs
Module: fs
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/@vscode/l10n@0.0.18
ℹ 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/@vscode/l10n@0.0.18. 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 @vscode/l10n with module fs/promises
Module: fs/promises
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/@vscode/l10n@0.0.18
ℹ 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/@vscode/l10n@0.0.18. 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 ajv-draft-04 was last published 5 years ago
Last Publish: 5/23/2021, 3:48:18 PM
From: ? → npm/@astrojs/check@0.9.10 → npm/ajv-draft-04@1.0.0
ℹ 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/ajv-draft-04@1.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 ajv-draft-04
URLs: http://json-schema.org/draft-04/schema, http://json-schema.org/schema
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/ajv-draft-04@1.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/ajv-draft-04@1.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 emmet
URLs: http://example.com, http://www.w3.org/1999/xhtml, http://www.w3.org/1999/XSL/Transform
Location: Package overview
From: ? → npm/@astrojs/check@0.9.10 → npm/emmet@2.4.11
ℹ 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/emmet@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.
|
|
See 43 more rows in the dashboard
|
