Bump security tooling & cryptography; eliminate Bandit B112 in TypeRegistry #90
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Description
pyproject.tomlto bumpcryptographyto>=46.0.0and dev tooling minimums:bandit>=1.9.3,safety>=3.7.0,semgrep>=1.149.0, andpip-audit>=2.10.0.datason/type_registry.pyto use local result variables (can_handle,matches,name) instead oftry/except/continue, preserving the previous skip-on-error semantics without triggering Bandit B112.rust/Cargo.lockfile from the tree.Testing
bandit -c pyproject.toml -r datason/and confirmed the prior B112 findings were cleared and the second scan reported no issues.bandit==1.9.3locally to run the scan, and the installation completed successfully.Codex Task