fingerprintjs2 (Valve)

---

What fingerprintjs2 (Valve) actually does

The v2-era repository, still linked from a great deal of older writing and still the version some deployed code depends on.

What fingerprintjs2 (Valve)'s maintenance signals mean

WITHDRAWN is the one state in this rubric that is not a judgment about time at all. The register requested this entry's address and got back a permanent redirect to https://github.com/fingerprintjs/fingerprintjs. That response is the maintainer's own statement about where the work moved, and a status code is a much stronger piece of evidence than a stale push date, which is why this clause is tested before any date rule.

Nothing is inferred here and nothing is deleted. The entry keeps its name, its description, its licence and its history, because a reader who arrives holding a link to the old address needs to be told what happened to it — and a register that quietly removes moved entries is a register you cannot audit against its own past printings.

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 fingerprintjs2 (Valve) sits in this catalogue

fingerprintjs2 (Valve) 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: FingerprintJS (ACTIVE), BotD (ACTIVE), ThumbmarkJS (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 WITHDRAWN. 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.

This register records that FingerprintJS supersedes fingerprintjs2 (Valve). Supersession here is declared, never inferred: it is printed only where a project or its author says so, because "newer" and "replaces" are not the same relation and treating them as one is how a list starts recommending rewrites nobody asked for.

The fingerprintjs2 (Valve) relations page sets every declared edge side by side on licence, push date, release cadence and derived state.

What to settle before you adopt fingerprintjs2 (Valve)

Its URL now answers with a permanent redirect to the current project, and that redirect is the maintainer's own statement about where the work went — which is exactly what the WITHDRAWN state records. Nothing here was inferred from silence.