| Block |
 |
Recently published: npm baseline-browser-mapping published 8 hours ago
Location: Package overview
From: yarn.lock → npm/webpack@5.109.2 → npm/@jest/globals@29.7.0 → npm/jest@29.7.0 → npm/baseline-browser-mapping@2.11.8
ℹ Read more on: This package | This alert | What are recently published artifacts?
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 either be allowlisted to allow recently-published versions, or an older version should be used instead.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/baseline-browser-mapping@2.11.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 |
|
Recently published: npm brace-expansion published 14 hours ago
Location: Package overview
From: yarn.lock → npm/@jest/globals@29.7.0 → npm/jest@29.7.0 → npm/brace-expansion@1.1.18
ℹ Read more on: This package | This alert | What are recently published artifacts?
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 either be allowlisted to allow recently-published versions, or an older version should be used instead.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/brace-expansion@1.1.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 |
|
Recently published: npm enhanced-resolve published 14 hours ago
Location: Package overview
From: yarn.lock → npm/webpack@5.109.2 → npm/enhanced-resolve@5.24.5
ℹ Read more on: This package | This alert | What are recently published artifacts?
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 either be allowlisted to allow recently-published versions, or an older version should be used instead.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/enhanced-resolve@5.24.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 |
|
Recently published: npm tldts-core published 37 minutes ago
Location: Package overview
From: yarn.lock → npm/msw@2.11.2 → npm/tldts-core@7.4.10
ℹ Read more on: This package | This alert | What are recently published artifacts?
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 either be allowlisted to allow recently-published versions, or an older version should be used instead.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/tldts-core@7.4.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 |
|
Recently published: npm tldts published 36 minutes ago
Location: Package overview
From: yarn.lock → npm/msw@2.11.2 → npm/tldts@7.4.10
ℹ Read more on: This package | This alert | What are recently published artifacts?
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 either be allowlisted to allow recently-published versions, or an older version should be used instead.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/tldts@7.4.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.
|
| Warn |
 |
License policy violation: npm caniuse-lite under CC-BY-4.0
Location: Package overview
From: yarn.lock → npm/webpack@5.109.2 → npm/@jest/globals@29.7.0 → npm/jest@29.7.0 → npm/caniuse-lite@1.0.30001806
ℹ Read more on: This package | This alert | What is a license policy violation?
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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/caniuse-lite@1.0.30001806. 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.
|
| Warn |
|
Obfuscated code: npm webpack is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: package.json → npm/webpack@5.109.2
ℹ Read more on: This package | This alert | What is obfuscated 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/webpack@5.109.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.
|
| Warn |
|
Obfuscated code: npm yargs is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: yarn.lock → npm/jest@29.7.0 → npm/msw@2.11.2 → npm/yargs@17.7.3
ℹ Read more on: This package | This alert | What is obfuscated 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/yargs@17.7.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.
|
| Warn |
|
Dynamic code execution: npm minimizer-webpack-plugin
Eval Type: Function
Location: Package overview
From: yarn.lock → npm/webpack@5.109.2 → npm/minimizer-webpack-plugin@5.6.1
ℹ 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/minimizer-webpack-plugin@5.6.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.
|
