No global holds an unnamed native function
No own property of window holds a native function whose name is empty (severity: warn).
What a detector infers
The DevTools protocol lets an automation client put a function on the page with Runtime.addBinding, so page code can call back into the client. The binding appears as a property of window whose value is a native function with an empty name. Chrome's own globals are all named after themselves, and functions a page defines are not native, so a nameless native function on window has no ordinary source.
Drivers that hide their bindings behind random property names still leave this shape. Measured on 2 November 2026 on Windows: genuine Chrome 156 and Clearcote under its SDK have no such global.
How to resolve it
Do not expose functions to the page through Runtime.addBinding (a driver's exposeFunction or exposeBinding) on pages that should look ordinary, or remove them before the page can enumerate window.
Nearby checks in Automation surface
- No console preview enumerated a prototype-chain Proxy
console-preview-proxy-trapDevTools has to look inside an object to show it to you, and in JavaScript looking inside an object is an observable act. - No Puppeteer / Playwright sourceURL marker
sourceurl-leakPuppeteer and Playwright evaluation labels can appear in main-world Error stacks. - No controller code crossed the main-world canary
main-world-executionAn early DOM canary records main-world calls, but page code and extensions can also call it, so this is contextual. - No exposed Puppeteer / Playwright binding
exposed-binding-leaksExposed functions leave Playwright/Puppeteer registries, prefixes, source text, or __installed markers. - The page itself arrived over a network protocol
document-arrived-over-networkEvery page keeps a navigation timing entry for its own document. - A popup opened without a user gesture is blocked
popup-blocked-without-gestureChrome blocks a window.open popup unless the page has a user activation, a click or key press in the last 5 seconds. - Content Security Policy is enforced
csp-bypassThe audit excludes data: scripts. Execution despite script-src is direct CSP-bypass behavior. - The browser will not resolve a filesystem path the page invented
synthesized-path-entry-sandboxThis row does not measure a fingerprint. It measures whether the browser will help a page enumerate what is installed on the machine, and it…
Clearcote is a browser built for fingerprint coherence
It is a Chromium fork, maintained by the same people who wrote this reference. It ships as a compiled browser rather than as a stealth script injected into someone else's — which is a description of how it is built, and is not an argument about how it behaves on this check.
This audit takes no position on how Clearcote scores on Automation surface checks, on this one, or anywhere else. It has no baseline corpus of other people's fingerprints to rank you against and no vendor scoreboard — nearly every check is self-referential, asking one browser the same question through two independent APIs and reporting whether both answers can be true at once. It runs identically on any browser, including ours. Run it on yours and read the result yourself.
See the other checks in Automation surface — the family no-unnamed-native-globals belongs to.