License policy violation: cargo lzma-sys under GPL-2.0+
License: GPL-2.0+ - The applicable license policy does not permit this license (5) (lzma-sys-0.1.20/xz-5.2/COPYING)
License: GPL-2.0-or-later - the applicable license policy does not allow this license (4) (lzma-sys-0.1.20/xz-5.2/COPYING)
License: GPL-3.0-or-later - the applicable license policy does not allow this license (4) (lzma-sys-0.1.20/xz-5.2/COPYING)
License: GPL-2.0-only - The applicable license policy does not permit this license (5) (lzma-sys-0.1.20/xz-5.2/COPYING)
License: GPL-3.0 - The applicable license policy does not permit this license (5) (lzma-sys-0.1.20/xz-5.2/COPYING)
License: GPL-2.0+ - The applicable license policy does not permit this license (5) (lzma-sys-0.1.20/xz-5.2/COPYING.GPLv2)
License: GPL-3.0 - The applicable license policy does not permit this license (5) (lzma-sys-0.1.20/xz-5.2/COPYING.GPLv3)
From: ? → cargo/world-id-primitives@0.11.0 → cargo/lzma-sys@0.1.20
ℹ 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 cargo/lzma-sys@0.1.20. 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.
