Merge iterate

[romeokienzler]

What changes were proposed in this pull request?

How was this pull request tested?

Developer's Certificate of Origin 1.1

   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

[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/​opencv-python-headless@​4.13.0.92
	pypi/​psycopg2-binary@​2.9.12
	pypi/​numpy@​2.5.0
	pypi/​mlflow@​3.14.0
	pypi/​torch@​2.12.1
	pypi/​gputil@​1.4.0
	pypi/​pillow@​12.2.0
	pypi/​pytest@​9.1.1
	pypi/​mkdocs-material@​9.7.6
	pypi/​asyncio@​4.0.0
	pypi/​scikit-learn@​1.9.0
	pypi/​pre-commit@​4.6.0
	pypi/​psutil@​7.2.2
	pypi/​terratorch@​1.2.8
	pypi/​coverage@​7.14.3
	pypi/​pytorch-lightning@​2.6.5
	pypi/​werkzeug@​3.1.8
	pypi/​urllib3@​2.7.0
	pypi/​aiohttp@​3.14.1
	pypi/​tox@​4.56.1
	pypi/​mike@​2.2.0
	pypi/​geobench@​1.0.0
	pypi/​jinja2@​3.1.6
	pypi/​optuna@​4.9.0
	pypi/​seaborn@​0.13.2
	pypi/​deepdiff@​9.1.0
	pypi/​configspace@​1.2.2
	pypi/​requests@​2.34.2
	pypi/​optuna-integration@​4.9.0
	pypi/​sqlparse@​0.5.5
	pypi/​pytest-cov@​7.1.0
	pypi/​ruff@​0.15.20
See 8 more rows in the dashboard

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		Obfuscated code: pypi mlflow is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pyproject.toml → pypi/mlflow@3.14.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/mlflow@3.14.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		Obfuscated code: pypi mlflow is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pyproject.toml → pypi/mlflow@3.14.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/mlflow@3.14.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		Obfuscated code: pypi numpy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pyproject.toml → pypi/numpy@2.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/numpy@2.5.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.

View full report