exception-swallowing
Silently swallowed exceptions hide bugs and make debugging hard
Applies to: C#, Go, JavaScript, Python, Ruby, Rust, TypeScript
Why this matters
When you catch an exception and do nothing with it, you're hiding potential bugs. The code might be failing silently, and you won't know until something goes seriously wrong. At minimum, log the error so you can debug issues.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, QUAL001 includedstablestack explain QUAL001False positive in your codebase? Suppress a single line with # noqa: QUAL001
More Code Quality checks
unnamed-thread
Threads without names are hard to identify in debugging tools
QUAL003complex-tuple
Tuples with 3+ elements are hard to understand - use a dataclass instead
QUAL004mutable-default-argument
Mutable default arguments are shared between calls and cause bugs
QUAL005print-statement
Print statements are typically debugging code that shouldn't be committed
QUAL006todo-comment
TODO/FIXME comments indicate incomplete or problematic code
QUAL007broad-exception
Catching all exceptions hides bugs and makes debugging hard
QUAL008magic-number
Magic numbers make code hard to understand and maintain
QUAL009file-too-long
File exceeds recommended maximum length.