Worker scopes available to compare against the window
Check id worker-scopes-reached
What an ordinary browser yields
An ordinary browser: at least the dedicated scope answers and is listed, usually alongside the shared scope — informational, never a fail. Listing only the dedicated scope is also ordinary: SharedWorker is absent or restricted in some perfectly normal configurations.
What a detector infers
This row asserts nothing — pass is hardcoded null and severity is info. It exists to frame every worker-vs-window comparison in this section by naming WHICH realms actually answered. The audit attempts a dedicated Worker and a SharedWorker in parallel, each from a blob: URL with a 2500ms timeout, and lists whichever resolved along with the `self.constructor.name` each one reported for its scope (e.g. DedicatedWorkerGlobalScope, SharedWorkerGlobalScope). If none answer, the detail says so explicitly: the comparisons are unavailable, not passing. This matters because a null result and a pass are different epistemic states, and a reader looking at 'Every worker realm reports the same identity' has to know whether that means 'we checked two realms and they agreed' or 'nothing answered'. Also note what is deliberately absent here: there is no worker-source or blob-scheme check, because the audit spawns its own probes from blob: URLs and such a check would flag the implementation itself on every run.
How to resolve it
Nothing to fix — this is a framing row. If it reports that no scope answered, the worker comparisons above it carry no evidence either way and should be read as unavailable rather than clean.
Other checks in Worker realms
- Every worker realm reports the same identity as the window
worker-realms-agreeA page is not one JavaScript realm — it is several. The audit loads one probe script into all three worker kinds the platform offers: a… - Every worker realm reports the same GPU as the window
worker-gpu-agreesInside each worker the probe creates an OffscreenCanvas(32,32), obtains a webgl (or experimental-webgl) context, and reads…
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 Worker realms 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 Worker realms — the family worker-scopes-reached belongs to.