Bump mypy from 2.3.1 to 2.4.0

[dependabot]

Bumps mypy from 2.3.1 to 2.4.0.

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next Release

Mypy 2.4

We've just uploaded mypy 2.4.0 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

Python 3.15 Support

Mypy 2.4 supports running on Python 3.15 and type checking most Python 3.15 features. This includes the new builtin sentinel type for sentinel values (PEP 661), which mypy now supports (see below for details). Lazy imports (PEP 810) and unpacking in comprehensions (PEP 798) are also supported. Closed TypedDicts (PEP 728) have been supported since mypy 2.2, but the extra_items TypedDict argument, also introduced in PEP 728, is still unsupported. Support for extra_items will be added in a future mypy release.

Native Parser Enabled by Default

Mypy now uses the new native parser by default. It's based on the Ruff parser, and it's significantly faster than the legacy parser, which uses the stdlib ast module. The native parser also has other benefits:

• You can target newer Python versions and use recent Python syntax even when running mypy on an older Python version. For example, you can use --python-version 3.15 when running mypy on Python 3.14.
• Stub files can use syntax that is newer than the target Python version. For example, stubs can use the PEP 695 generic class syntax (class Box[T]: ...) when running on or targeting Python 3.10.
• Parallel type checking requires the native parser.

The legacy parser is still available through --no-native-parser, or native_parser = False in the config file (native_parser = false under [tool.mypy] in pyproject.toml). We are planning to remove the legacy parser in early 2027. If you run into a problem with the native parser, please report it on the issue tracker.

Unlike the legacy parser, the native parser doesn't support type comments for variables defined by for and with statements. These type comments are silently ignored, and the types of the variables are

... (truncated)

Commits

• 935ba8a Bump version to 2.4.0
• 334a678 Add link for PR 22066 in mypy 2.4 changelog (#22082)
• fe69660 Finalize mypy 2.4 changelog (#22080)
• 541fd87 Various mypy 2.4 changelog updates (#22077)
• b231182 Update native parser docs (#22078)
• 04fe42c Initial Changelog for Mypy 2.4 (#22071)
• 0617494 Quick fix for non UTF-8 encodings with new parser (#22066)
• b2f9b60 Bump librt to 0.16.0 (#22067)
• 9d798dc Sync typeshed (#22054)
• 0861bb6 Reduce max protocol stack size to 20 (#22053)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Note

Low Risk
Dev-only tooling version bump with no production code changes; possible new or changed mypy findings after upgrade.

Overview
Bumps the dev optional dependency mypy from 2.3.1 to 2.4.0 in pyproject.toml. No application runtime or production dependency changes.

CI and local type checking (including pre-commit mypy) will run the newer release, which enables the native parser by default and may report different diagnostics than 2.3.1.

^{Reviewed by Cursor Bugbot for commit c9af3cc. Bugbot is set up for automated code reviews on this repo. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pypi/​mypy@​2.3.1 ⏵ 2.4.0	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Priority	Alert  (click "▶" to expand/collapse)	Action
	License policy violation: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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: pypi mypy License: LicenseRef-scancode-python-cwi - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) License: LicenseRef-BeOpen-Python-2.0 - The applicable license policy does not permit this license (5) (mypy-2.4.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/mypy@2.4.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 pypi/mypy@2.4.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
See 29 more rows in the dashboard

View full report