CreepJS worker tests

---

What CreepJS worker tests actually does

The worker-scope subset of the same suite. A worker has its own global object and its own copy of the surfaces a page patches, so a spoofing layer applied only to the document leaves the worker telling the truth.

What can and cannot be measured about CreepJS worker tests

This entry has no repository, so none of the usual repository fields exist for it — no push date, no release tag, no archive flag, no licence identifier. Its state comes from one measurement only: the register requested the address and recorded what came back. Anything in the range 200 to 399 makes a non-repository entry ACTIVE, and that clause is the one the first edition of the rubric did not have at all, which is why live page entries carried no state under it.

Read that for exactly what it is. It says the thing is reachable. It does not say the page still works correctly, because no HTTP status can carry that. Where a stronger signal exists — a repository, a version, a dated revision — this register prefers it, and where one does not, it prints the weaker signal and names it as weak rather than dressing it up.

Where CreepJS worker tests sits in this catalogue

CreepJS worker tests is filed in section 03, detection test pages & fingerprint scanners, whose scope is this: Pages you point a browser at to see what it gives away. This section is where a link register earns its keep: test pages rot faster than repositories. An entry sits in exactly one section here. Where a project could defensibly go in two, it is placed where a reader would look for it first rather than where it fits most tidily, and that is an editorial decision rather than a measured one.

Filed beside it in the same section: CreepJS (live) (ACTIVE), BrowserLeaks (ACTIVE), BrowserLeaks TLS (ACTIVE). Comparing an entry against its own section-mates is more informative than comparing it against the catalogue as a whole, because everything in a section is answering roughly the same question and the differences left over are the ones that matter.

There is no licence field, because there is no source to licence — this is a live page rather than a code repository. It is grouped instead with every other entry the rubric marks ACTIVE, which is the axis that actually distinguishes entries of this kind from one another.

What to settle before you adopt CreepJS worker tests

This is the specific gap most page-script stealth stacks have, which makes it the most informative single page in this section for anyone using one. Compare the two contexts' answers rather than reading either alone.