JavaScript logs
Silktide records the messages your pages write to the browser console while loading. These are usually debugging output left in by developers, and are worth reviewing to make sure they don't reveal information you'd rather keep private.
Why this matters
Console messages are visible to anyone who opens their browser's developer tools. Debugging output left in production can leak things you never meant to publish: internal URLs and file paths, configuration values, user data, or commentary about how your systems work. It is also noise that makes real errors harder to spot when a developer is diagnosing a problem.
Log messages don't break anything by themselves - this check is about hygiene and what your website discloses, not about functionality.
How to fix it
These findings are for a developer to review:
- Read each recorded message and judge whether it reveals anything sensitive or points at an underlying fault.
- Remove debugging output from your own code before publishing - statements
like
console.log(...)rarely belong in production. Many build tools can strip them automatically. - Messages from third-party scripts are usually harmless and outside your control. findings that are fine so they aren't raised again.
How Silktide tests this
- Load each page in a real browser, running scripts just as a visitor's browser would.
- Record every ordinary console message the page writes while loading - log, informational, debug, and trace output - whether from your code or third-party scripts. Errors and warnings are covered by the separate JavaScript errors check.
- Report each message with a stack trace showing where it originated.
Troubleshooting
Most of the messages come from third-party scripts
Common - many popular scripts announce themselves in the console. You can't remove their messages without removing the script, so review them once and approve them.
A message only appears sometimes
Scripts can log conditionally, for example only when a request is slow or a feature flag is set. The recorded stack trace shows what produced the message during Silktide's visit.