Skip to content

Ruff

903 rules ruff@0.17.0

Complete effective rule inventory.

Docs

Rules

32 rules on this page · 903 total

  • S102

    Use of exec detected

    No autofix
  • S103

    os.chmod setting a permissive mask {mask:#o} on file or directory

    No autofix
  • S104

    Possible binding to all interfaces

    No autofix
  • S105

    Possible hardcoded password assigned to: "{}"

    No autofix
  • S106

    Possible hardcoded password assigned to argument: "{}"

    No autofix
  • S107

    Possible hardcoded password assigned to function default: "{}"

    No autofix
  • S108

    Probable insecure usage of temporary file or directory: "{}"

    No autofix
  • S110

    try-except-pass detected, consider logging the exception

    No autofix
  • S112

    try-except-continue detected, consider logging the exception

    No autofix
  • S113

    Probable use of {module} call without timeout

    No autofix
  • S201

    Use of debug=True in Flask app detected

    No autofix
  • S202

    Uses of tarfile.extractall()

    No autofix
  • S301

    pickle and modules that wrap it can be unsafe when used to deserialize untrusted data, possible security issue

    No autofix
  • S302

    Deserialization with the marshal module is possibly dangerous

    No autofix
  • S303

    Use of insecure MD2, MD4, MD5, or SHA1 hash function

    No autofix
  • S304

    Use of insecure cipher, replace with a known secure cipher such as AES

    No autofix
  • S305

    Use of insecure block cipher mode, replace with a known secure mode such as CBC or CTR

    No autofix
  • S306

    Use of insecure and deprecated function (mktemp)

    No autofix
  • S307

    Use of possibly insecure function; consider using ast.literal_eval

    No autofix
  • S308

    Use of mark_safe may expose cross-site scripting vulnerabilities

    No autofix
  • S310

    Audit URL open for permitted schemes. Allowing use of file: or custom schemes is often unexpected.

    No autofix
  • S311

    Standard pseudo-random generators are not suitable for cryptographic purposes

    No autofix
  • S312

    Telnet is considered insecure. Use SSH or some other encrypted protocol.

    No autofix
  • S313

    Using xml to parse untrusted data is known to be vulnerable to XML attacks; use defusedxml equivalents

    No autofix
  • S314

    Using xml to parse untrusted data is known to be vulnerable to XML attacks; use defusedxml equivalents

    No autofix
  • S315

    Using xml to parse untrusted data is known to be vulnerable to XML attacks; use defusedxml equivalents

    No autofix
  • S316

    Using xml to parse untrusted data is known to be vulnerable to XML attacks; use defusedxml equivalents

    No autofix
  • S317

    Using xml to parse untrusted data is known to be vulnerable to XML attacks; use defusedxml equivalents

    No autofix
  • S318

    Using xml to parse untrusted data is known to be vulnerable to XML attacks; use defusedxml equivalents

    No autofix
  • S319

    Using xml to parse untrusted data is known to be vulnerable to XML attacks; use defusedxml equivalents

    No autofix
  • S321

    FTP-related functions are being called. FTP is considered insecure. Use SSH/SFTP/SCP or some other encrypted protocol.

    No autofix
  • S323

    Python allows using an insecure context via the _create_unverified_context that reverts to the previous behavior that does not validate certificates or perform hostname checks.

    No autofix