Broprint.js

---

What Broprint.js actually does

A small visitor identifier built on canvas and audio readings only, which makes it a compact demonstration of how few surfaces are needed to get a usable identifier.

What Broprint.js's maintenance signals mean

pushed_at reads 2026-04-25, which is 111 days before the field check and therefore inside the 90-to-365-day band this rubric calls SEMI. SEMI is the first edition's ACTIVE bucket after it was split in two, and the split exists because a quarter of silence in this field is a fact worth printing rather than absorbing.

A SEMI entry is not a warning and not a recommendation. It is a request to look: open the commit history and see whether the gap is a maintainer between jobs, a project that has reached a stable shape and stopped needing changes, or an abandonment that has not yet crossed a threshold. All three produce the same field value, and this register cannot tell them apart — it can only make sure you know the gap is there.

No release was captured for this entry, which this register records as unknown rather than as none. The distinction matters more than it looks: a project with no tags and a project whose tags the sweep failed to read produce the same blank cell, and printing them as the same fact would be the register asserting something it has not measured.

Where Broprint.js sits in this catalogue

Broprint.js is filed in section 06, fingerprinting libraries, whose scope is this: The collectors themselves — the code that reads a browser. Read these to know what is being asked of you. 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 (source) (ACTIVE), detectIncognito (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.

It is published under MIT, alongside the rest of the MIT entries in this register, and it sits with everything else currently marked SEMI. Read those two facets together: a permissively licensed project that stopped shipping is not a safer dependency than a copyleft one that did not, and a filter on one axis alone will tell you the wrong thing.

What to settle before you adopt Broprint.js

A two-surface fingerprint is easier to defeat and easier to understand, and it is the second property that makes it worth reading. For production identification it is doing much less than the larger libraries here.