Every check / code-ships-debug-output

Does your live site still carry the code used to debug it?

We read the script files your site serves from its own domain for debugger statements and for console.log, debug, trace and dir calls.

How it decides

The check speaks up at any debugger statement, or at fifteen or more console calls, since a handful is normal.

Run this check on any website

Free, with no account. It sends the site nothing an ordinary visitor would not.

Why it matters

A debugger statement freezes the page for anyone with developer tools open.

In more detail

Console messages often carry internal values, customer details or system paths, and a build that leaves either in is not configured for production. Every bundler has an option that strips them.

Who fixes it, and where it runs

Who usually fixes it
Whoever built your site
Which plan runs it
The free scan, on any website
Proof you own the site
Not needed. It sends your site nothing an ordinary visitor would not.
More about this check
Who it is about
An intruder
Listed under
Outside code your site runs
Its name in a report
code-ships-debug-output