 |
High CVE: npm adm-zip: Unhandled error event in async DEFLATE decompression crashes Node.js process (DoS)
CVE: GHSA-8238-w5pm-2374 adm-zip: Unhandled error event in async DEFLATE decompression crashes Node.js process (DoS) (HIGH)
Affected versions: < 0.6.1
Patched version: 0.6.1
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/adm-zip@0.6.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/adm-zip@0.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 |
 |
High CVE: npm adm-zip: Decompression-bomb protection (fix for CVE-2026-39244) can be bypassed by declaring uncompressed size as 0
CVE: GHSA-rcw4-f5rp-g42v adm-zip: Decompression-bomb protection (fix for CVE-2026-39244) can be bypassed by declaring uncompressed size as 0 (HIGH)
Affected versions: < 0.6.1
Patched version: 0.6.1
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/adm-zip@0.6.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/adm-zip@0.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 |
 |
High CVE: npm adm-zip extraction preserves SUID/SGID bits from untrusted ZIPs -> local privilege escalation
CVE: GHSA-j5f4-cc29-5x44 adm-zip extraction preserves SUID/SGID bits from untrusted ZIPs -> local privilege escalation (HIGH)
Affected versions: < 0.6.1
Patched version: 0.6.1
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/adm-zip@0.6.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/adm-zip@0.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 |
 |
High CVE: npm adm-zip: Uncontrolled memory allocation via the declared uncompressed size (DoS)
CVE: GHSA-7q85-xj36-vmfc adm-zip: Uncontrolled memory allocation via the declared uncompressed size (DoS) (HIGH)
Affected versions: < 0.6.1
Patched version: 0.6.1
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/adm-zip@0.6.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/adm-zip@0.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 |
 |
High CVE: Axios: Prototype Pollution Gadget in npm axios toFormData Options
CVE: GHSA-x97p-jq2g-jp4f Axios: Prototype Pollution Gadget in axios toFormData Options (HIGH)
Affected versions: >= 0.28.0 < 0.34.0; >= 1.15.1 < 1.20.0
Patched version: 1.20.0
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/axios@1.18.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/axios@1.18.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 |
 |
High CVE: Axios: Node HTTP adapter prototype-pollution gadget allows request socket hijack via inherited createConnection
CVE: GHSA-m8m8-qj5v-23w3 Axios: Node HTTP adapter prototype-pollution gadget allows request socket hijack via inherited createConnection (HIGH)
Affected versions: >= 1.15.2 < 1.20.0
Patched version: 1.20.0
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/axios@1.18.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/axios@1.18.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 |
 |
High CVE: Axios: maxRedirects: 0 is not enforced by the fetch adapter, allowing redirect-based SSRF
CVE: GHSA-r4gj-5m52-g5wh Axios: maxRedirects: 0 is not enforced by the fetch adapter, allowing redirect-based SSRF (HIGH)
Affected versions: >= 1.17.0 < 1.20.0
Patched version: 1.20.0
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/axios@1.18.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/axios@1.18.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 |
 |
High CVE: Axios: Denial of Service via Unhandled 'error' Event in HTTP/2 ClientHttp2Session Initialization
CVE: GHSA-542g-h47m-68v8 Axios: Denial of Service via Unhandled 'error' Event in HTTP/2 ClientHttp2Session Initialization (HIGH)
Affected versions: >= 1.13.0 < 1.20.0
Patched version: 1.20.0
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/axios@1.18.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/axios@1.18.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 |
 |
High CVE: Axios: ReDoS in fromDataURI data: URL parser freezes the Node event loop (DoS)
CVE: GHSA-c29m-xwm3-cm6r Axios: ReDoS in fromDataURI data: URL parser freezes the Node event loop (DoS) (HIGH)
Affected versions: >= 1.16.1 < 1.20.0
Patched version: 1.20.0
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/axios@1.18.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/axios@1.18.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 |
 |
High CVE: Axios: HTTP/2 adapter bypasses configured DNS lookup and proxy controls
CVE: GHSA-3pq3-5fj3-cg6v Axios: HTTP/2 adapter bypasses configured DNS lookup and proxy controls (HIGH)
Affected versions: >= 1.13.0 < 1.20.0
Patched version: 1.20.0
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/axios@1.18.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/axios@1.18.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 |
 |
High CVE: Axios: ReDoS (O(N²)) in shouldBypassProxy host normalization, reachable via untrusted redirect Location
CVE: GHSA-mghh-pgcx-3jjj Axios: ReDoS (O(N²)) in shouldBypassProxy host normalization, reachable via untrusted redirect Location (HIGH)
Affected versions: >= 1.15.0 < 1.20.0
Patched version: 1.20.0
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/axios@1.18.0
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/axios@1.18.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 |
 |
High CVE: npm sharp: Vulnerabilities in libheif: GHSA-g89c-p67h-r497 and GHSA-2jg2-4ch7-h545
CVE: GHSA-rgj7-g3m4-5g8c sharp: Vulnerabilities in libheif: GHSA-g89c-p67h-r497 and GHSA-2jg2-4ch7-h545 (HIGH)
Affected versions: < 0.35.4
Patched version: 0.35.4
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/sharp@0.33.5
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/sharp@0.33.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.
|
Warn |
 |
High CVE: npm sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591
CVE: GHSA-f88m-g3jw-g9cj sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591 (HIGH)
Affected versions: < 0.35.0
Patched version: 0.35.0
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/sharp@0.33.5
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/sharp@0.33.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.
|
Warn |
 |
High CVE: npm sharp : Vulnerability in librsvg dependency CVE-2026-96889
CVE: GHSA-wq5f-xc86-pv6w sharp : Vulnerability in librsvg dependency CVE-2026-96889 (HIGH)
Affected versions: < 0.35.5
Patched version: 0.35.5
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/sharp@0.33.5
ℹ Read more on: This package | This alert | What is a CVE?
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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/sharp@0.33.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.
|
Warn |
 |
License policy violation: npm @img/sharp-wasm32
Location: Package overview
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/@img/sharp-wasm32@0.33.5
ℹ 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/@img/sharp-wasm32@0.33.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.
|
Warn |
 |
License policy violation: npm @mintlify/cli under Elastic-2.0
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE)
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/@mintlify/cli@4.0.1665
ℹ 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/@mintlify/cli@4.0.1665. 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 @mintlify/common under Elastic-2.0
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE)
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/@mintlify/common@1.0.1260
ℹ 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/@mintlify/common@1.0.1260. 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 @mintlify/link-rot under Elastic-2.0
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE)
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/@mintlify/link-rot@3.0.1481
ℹ 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/@mintlify/link-rot@3.0.1481. 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 @mintlify/models under Elastic-2.0
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE)
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/@mintlify/models@0.0.375
ℹ 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/@mintlify/models@0.0.375. 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 @mintlify/og under Elastic-2.0
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE)
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/@mintlify/og@0.0.58
ℹ 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/@mintlify/og@0.0.58. 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 @mintlify/package-builder under Elastic-2.0
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE)
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/@mintlify/package-builder@0.0.48
ℹ 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/@mintlify/package-builder@0.0.48. 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 @mintlify/prebuild under Elastic-2.0
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE)
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/@mintlify/prebuild@1.0.1425
ℹ 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/@mintlify/prebuild@1.0.1425. 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 @mintlify/previewing under Elastic-2.0
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (npm metadata)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/package.json)
License: Elastic-2.0 - The applicable license policy does not permit this license (5) (package/LICENSE)
From: pnpm-lock.yaml → npm/mint@4.2.1062 → npm/@mintlify/previewing@4.0.1501
ℹ 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/@mintlify/previewing@4.0.1501. 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 |
|
See 18 more rows in the dashboard
|