Will It Vibe?printStackTrace() used instead of logging the exception
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
e.printStackTrace() writes directly to stderr instead of through a logger, so the failure bypasses log levels, structured fields, and log aggregation, and can be lost entirely if stderr is not captured.
Why it matters
printStackTrace() writes directly to stderr instead of through the logging framework, so the exception detail is not level-filtered, has no structured fields for log aggregation, and can be lost entirely if stderr is not captured by whatever is running the process.
How to fix it
Log the exception through the project's logger, passing the exception object itself (not just its message) so the stack trace is preserved in the log record: logger.error("some context", e).
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo