| 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/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 ansi-regex with https://github.com
URLs: https://github.com
Location: Package overview
From: ? → npm/ansi-regex@5.0.1
ℹ 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/ansi-regex@5.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 |
|
Unmaintained: npm cuint was last published 10 years ago
Last Publish: 8/23/2016, 7:15:38 PM
From: ? → npm/cuint@0.2.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/cuint@0.2.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 |
|
Unmaintained: npm get-caller-file was last published 7 years ago
Last Publish: 3/9/2019, 9:48:30 PM
From: ? → npm/get-caller-file@2.0.5
ℹ 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/get-caller-file@2.0.5. 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 prettier in module module
Module: module
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Debug access: npm prettier in module v8
Module: v8
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Dynamic module loading: npm prettier
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Environment variable access: npm prettier
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Environment variable access: npm prettier reads NODE_DEBUG
Env Vars: NODE_DEBUG
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Environment variable access: npm prettier reads npm_package_name
Env Vars: npm_package_name
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Environment variable access: npm prettier reads npm_lifecycle_script
Env Vars: npm_lifecycle_script
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Environment variable access: npm prettier reads TEST_PSEUDOMAP
Env Vars: TEST_PSEUDOMAP
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Environment variable access: npm prettier reads _nodeLRUCacheForceNoSymbol
Env Vars: _nodeLRUCacheForceNoSymbol
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Environment variable access: npm prettier reads FORCE_COLOR
Env Vars: FORCE_COLOR
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Environment variable access: npm prettier reads PRETTIER_DEBUG
Env Vars: PRETTIER_DEBUG
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Filesystem access: npm prettier with module fs/promises
Module: fs/promises
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Filesystem access: npm prettier with module fs
Module: fs
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 prettier with 100.0% likelihood
Confidence: 1.00
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Embedded URLs or IPs: npm prettier
URLs: statement_parser.ml, flow_lexer.ml, camlinternalOO.ml, wtf8.ml, flow_sedlexing.ml, parser_env.ml, expression_parser.ml, parser_flow.ml, https://github.com/microsoft/TypeScript/issues/29729#issuecomment-700527227, https://github.com/prettier/prettier/blob/next/src/common/ast-path.js, https://prettier.io/docs/configuration, e.next?.type===, e.openStrip.open?, e.closeStrip.open?, e.inverseStrip.open?, https://prettier.io/docs/plugins#optional-embed, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode., https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/, https://aka.ms/tsconfig, https://typescript-eslint.io/troubleshooting/faqs/general#the-key-property-is-deprecated-on-type-nodes-use-key-instead-warnings., https://www.w3.org/TR/html5/syntax.html#closing-elements-that-have-implied-end-tags, SemVer.compare, https://github.com/jedmao/, http://treyhunner.com, git://github.com/editorconfig/editorconfig-core-js.git, https://github.com/editorconfig/editorconfig-core-js/issues, https://git-scm.com/docs/gitignore, https://git-scm.com/docs/gitignore/2.22.1, https://registry.npmjs.org/, css.global, n.rest?, n.id?, e.property?e.property.type===, https://evilmartians.com/chronicles/postcss-8-plugin-migration, t.value.group?.type===, t.open?.value===, https://yarnpkg.com/en/docs/selective-version-resolutions, https://git.io/vg5Ft, contents.lr, text.md
Location: Package overview
From: ? → npm/@astrojs/check@0.9.8 → npm/prettier@3.8.2
ℹ 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/prettier@3.8.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 |
|
Dynamic module loading: npm require-directory
Location: Package overview
From: ? → npm/require-directory@2.1.1
ℹ 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/require-directory@2.1.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 |
|
Filesystem access: npm require-directory with module fs
Module: fs
Location: Package overview
From: ? → npm/require-directory@2.1.1
ℹ 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/require-directory@2.1.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 require-directory was last published 11 years ago
Last Publish: 5/28/2015, 8:31:04 AM
From: ? → npm/require-directory@2.1.1
ℹ 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/require-directory@2.1.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 |
|
Embedded URLs or IPs: npm strip-ansi with https://github.com
URLs: https://github.com
Location: Package overview
From: ? → npm/strip-ansi@6.0.1
ℹ 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/strip-ansi@6.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 |
|
Embedded URLs or IPs: npm vscode-json-languageservice
URLs: https://github.com/microsoft/vscode/issues/42544, http://json-schema.org/draft-03/schema, https://json-schema.org/draft/2019-09/schema, http://json-schema.org/schema#, http://json-schema.org/draft-07/schema#, http://json-schema.org/draft-04/schema#, schema.json.id, schema.json.properties, http://daringfireball.net/projects/markdown/syntax#backslash, https://daringfireball.net/projects/markdown/syntax#precode
Location: Package overview
From: ? → npm/vscode-json-languageservice@4.1.8
ℹ 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-json-languageservice@4.1.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.
|
