Device and Browser Info datasets

---

What Device and Browser Info datasets actually does

Published device and browser attribute datasets with an API in front of them, which makes them usable as a comparison baseline in code rather than only as a page to read.

What can and cannot be measured about Device and Browser Info datasets

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 dataset 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 Device and Browser Info datasets sits in this catalogue

Device and Browser Info datasets is filed in section 08, datasets, leaderboards & public statistics, whose scope is this: Published distributions and population data. The only place in this catalogue where a percentage means anything, because someone else measured it and says how. 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: tlsfingerprint.io (ACTIVE), JA4 Database (ACTIVE), HTTP Archive reports (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 dataset 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 Device and Browser Info datasets

As with every corpus in this section, the collection method determines what the numbers mean and should be established before the numbers are used. This register publishes no distribution of its own to check them against.