| Block |
 |
Recently published: npm @dotenvx/dotenvx published 3 hours ago
Location: Package overview
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/@dotenvx/dotenvx@1.61.2
ℹ 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/@dotenvx/dotenvx@1.61.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 |
|
Recently published: npm axios published 2 hours ago
Location: Package overview
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/axios@1.15.2
ℹ 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/axios@1.15.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 |
|
Recently published: npm electron-to-chromium published 6 hours ago
Location: Package overview
From: ? → npm/@vitejs/plugin-react@5.2.0 → npm/@webflow/webflow-cli@1.14.0 → npm/electron-to-chromium@1.5.341
ℹ 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/electron-to-chromium@1.5.341. 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 jsonfile published yesterday
Location: Package overview
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/jsonfile@6.2.1
ℹ 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/jsonfile@6.2.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 |
|
Recently published: npm tapable published 7 hours ago
Location: Package overview
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/tapable@2.3.3
ℹ 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/tapable@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.
|
| Warn |
 |
License policy violation: npm caniuse-lite under CC-BY-4.0
Location: Package overview
From: ? → npm/@vitejs/plugin-react@5.2.0 → npm/@webflow/webflow-cli@1.14.0 → npm/caniuse-lite@1.0.30001788
ℹ 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.30001788. 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 lodash under CC0-1.0 AND MIT
Location: Package overview
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/lodash@4.18.1
ℹ 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/lodash@4.18.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.
|
| Warn |
|
License policy violation: npm memfs under Unlicense
Location: Package overview
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/memfs@3.6.0
ℹ 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/memfs@3.6.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.
|
| Warn |
|
License policy violation: npm vite
Location: Package overview
From: tooltip-hover-card/package.json → npm/vite@7.3.2
ℹ 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/vite@7.3.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 |
|
Dynamic code execution: npm async-generator-function
Eval Type: Function
Location: Package overview
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/async-generator-function@1.0.0
ℹ 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/async-generator-function@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.
|
| Warn |
|
Dynamic code execution: npm generator-function
Eval Type: Function
Location: Package overview
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/generator-function@2.0.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/generator-function@2.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.
|
| Warn |
|
Dynamic code execution: npm glob-to-regex.js
Eval Type: Function
Location: Package overview
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/glob-to-regex.js@1.2.0
ℹ 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/glob-to-regex.js@1.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.
|
| Warn |
|
Deprecated by its maintainer: npm koa-compose
Reason: koa-compose@4.2.0 is a breaking version, please either use <= v4.1 or upgrade to v5.x once it is released
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/koa-compose@4.2.0
ℹ Read more on: This package | This alert | What is a deprecated package?
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: Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/koa-compose@4.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.
|
| Warn |
|
Deprecated by its maintainer: npm memfs with reason "this will be v4"
Reason: this will be v4
From: ? → npm/@webflow/webflow-cli@1.14.0 → npm/memfs@3.6.0
ℹ Read more on: This package | This alert | What is a deprecated package?
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: Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/memfs@3.6.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.
|
