Ruff: add more safe TRY rules

[kiblik]

Self-descriptive

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Configured Codepaths Analyzer	✅	0 findings
Sensitive Files Analyzer	✅	0 findings
AppSec Analyzer	✅	0 findings
Authn/Authz Analyzer	✅	0 findings
Secrets Analyzer	✅	0 findings

Note

🟢 Risk threshold not exceeded.

Change Summary (click to expand)

The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective.

Summary:

The provided code change is an update to the ruff.toml configuration file, which is used by the Ruff linter, a fast and powerful Python linter. The key changes in this pull request are the addition of new linting rules, particularly those related to exception handling (TRY003, TRY302, TRY004, TRY2). From an application security perspective, the inclusion of these TRY rules suggests that the codebase may be handling exceptions or errors in a way that could be improved. Proper exception handling is crucial for maintaining application stability and preventing security vulnerabilities, such as those related to error handling or information disclosure. The other changes, such as the addition of SLOT, PD, PGH, FLY, NPY, and AIR rules, are likely related to other coding style and best practices enforced by the Ruff linter. Overall, this code change appears to be focused on improving the code quality and consistency of the codebase by adding more linting rules, with a particular emphasis on exception handling.

Files Changed:

• ruff.toml: The ruff.toml configuration file has been updated to include new linting rules, particularly those related to exception handling (TRY003, TRY302, TRY004, TRY2). These rules likely check for specific types of try-except blocks or exception handling patterns, which is an important aspect of secure coding practices. Additionally, other new rules, such as SLOT, PD, PGH, FLY, NPY, and AIR, have been added to enforce various coding style and best practices.

Powered by DryRun Security

[mtesauro]

Approved