print-statement
Print statements are typically debugging code that shouldn't be committed
Applies to: Go, JavaScript, Python, Ruby, Rust, TypeScript
Why this matters
print() and console.log() are usually leftover debugging code. In production, they clutter logs, can expose sensitive data, and indicate incomplete cleanup. Use a proper logging framework instead.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, QUAL005 includedstablestack explain QUAL005QUAL005 is part of the Pro rule set. See pricing — the free tier ships 24 checks with no signup.
False positive in your codebase? Suppress a single line with # noqa: QUAL005
More Code Quality checks
exception-swallowing
Silently swallowed exceptions hide bugs and make debugging hard
QUAL002unnamed-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
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.