chore: refresh all Python dependencies

[dependabot]

Refreshes every eligible dependency under the repository's 7-day stability window.

Direct updates include Ruff 0.16.2 and Coverage 7.15.4. The lock refresh also updates annotated-types, ast-serialize, certifi, httpx-aiohttp, librt, packaging, time-machine, typing-inspection, and yarl. This supersedes #48.

The generated pip fallback lock now keeps exact pins without redundant annotations. The coverage verifier is data-driven and smaller while preserving both thresholds and invalid-report checks.

Validation:

• Ruff, Pyright, MyPy, and import checks pass
• 9,074 tests pass across Python 3.10/3.14 and Pydantic 1/2
• statement coverage: 94.91%
• branch coverage: 81.03%
• pip-audit reports no known vulnerabilities
• wheel and source archives are reproducible

[kriptoburak]

Verified the full lock refresh locally across all supported Python and Pydantic test combinations. Lint, types, coverage, vulnerability audit, and reproducibility all pass.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	coverage@​7.15.3 ⏵ 7.15.4
	httpx-aiohttp@​0.1.12 ⏵ 0.2.0
	time-machine@​3.2.0 ⏵ 3.4.0	+1
	ruff@​0.16.1 ⏵ 0.16.2	+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.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: pypi certifi under MPL-2.0 License: MPL-2.0 - The applicable license policy does not permit this license (5) (certifi-2026.7.22/certifi.egg-info/PKG-INFO) License: MPL-2.0 - The applicable license policy does not permit this license (5) (certifi-2026.7.22/certifi.egg-info/PKG-INFO) License: MPL-2.0 - The applicable license policy does not permit this license (5) (certifi-2026.7.22/setup.py) License: MPL-2.0 - The applicable license policy does not permit this license (5) (certifi-2026.7.22/setup.py) License: MPL-2.0 - The applicable license policy does not permit this license (5) (certifi-2026.7.22/LICENSE) License: MPL-2.0 - The applicable license policy does not permit this license (5) (certifi-2026.7.22/PKG-INFO) License: MPL-2.0 - The applicable license policy does not permit this license (5) (certifi-2026.7.22/PKG-INFO) From: uv.lock → pypi/httpx@0.28.1 → pypi/certifi@2026.7.22 ℹ 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/certifi@2026.7.22. 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 certifi under MPL-2.0 License: MPL-2.0 - The applicable license policy does not permit this license (5) (certifi-2026.7.22.dist-info/METADATA) License: MPL-2.0 - The applicable license policy does not permit this license (5) (certifi-2026.7.22.dist-info/METADATA) License: MPL-2.0 - The applicable license policy does not permit this license (5) (certifi-2026.7.22.dist-info/licenses/LICENSE) From: uv.lock → pypi/httpx@0.28.1 → pypi/certifi@2026.7.22 ℹ 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/certifi@2026.7.22. 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 httpx-aiohttp under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (httpx_aiohttp-0.2.0/PKG-INFO) License: BSD-3-Clause - The applicable license policy does not permit this license (5) (httpx_aiohttp-0.2.0/LICENSE) From: pyproject.toml → pypi/httpx-aiohttp@0.2.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/httpx-aiohttp@0.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		License policy violation: pypi httpx-aiohttp under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (httpx_aiohttp-0.2.0.dist-info/METADATA) License: BSD-3-Clause - The applicable license policy does not permit this license (5) (httpx_aiohttp-0.2.0.dist-info/licenses/LICENSE) From: pyproject.toml → pypi/httpx-aiohttp@0.2.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/httpx-aiohttp@0.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		License policy violation: pypi librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0/LICENSE) License: 0BSD - The applicable license policy does not permit this license (5) (librt-0.15.0/pythoncapi_compat.h) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-2-Clause License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-2-Clause License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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 librt under BSD-3-Clause License: BSD-3-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: BSD-2-Clause - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: CNRI-Python-GPL-Compatible - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: PSF-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) License: Python-2.0 - The applicable license policy does not permit this license (5) (librt-0.15.0.dist-info/licenses/LICENSE) From: uv.lock → pypi/mypy@2.3.0 → pypi/librt@0.15.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/librt@0.15.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.
See 119 more rows in the dashboard

View full report