`console.log` (or `print`, in other languages) left in production code after debugging.
Each example shows the exact code shape the rule is looking for, then the smallest version that keeps the intent without hiding risk or adding noise.
function reconcile(orders: Order[]) {
console.log('reconciling', orders.length)
for (const o of orders) {
console.log('processing', o.id, o)
process(o)
}
}Deterministic AST match against debug-print calls (`console.log`, language equivalents) outside designated logging.
function reconcile(orders: Order[]) {
log.debug('reconciling', { count: orders.length })
for (const o of orders) {
process(o)
}
}Remove temporary debug output or replace it with the project's structured logger at the correct level. Include stable fields, not raw objects dumped from a debugging session.
Agents trace execution with console.log during a session and forget to remove them. The logs end up shipped — noisy, untyped, ungrep-able.
ai-slop/console-leftover
ai-slop
Deterministic AST match against debug-print calls (`console.log`, language equivalents) outside designated logging.
Calls through a structured logger, and console use inside CLI tools or test setup, are not flagged.
Provenance: repeated across public scans as debug output left in production paths.