The listed URL answers with a permanent redirect to somewhere else. That is the maintainer telling you where the work went, and it is the strongest liveness field there is.
The rule that sets it, second edition:
the URL answers with a permanent redirect to another entry.
Why WITHDRAWN: The URL answered 301 to https://github.com/fingerprintjs/fingerprintjs. The source moved the entry itself.
Field
Value at this printing
pushed_at
—
archived
false
latest_release
—
license.spdx_id
MIT
stargazers_count
—
http_status
301
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: GET https://api.github.com/repos/Valve/fingerprintjs2
Permanent redirect to fingerprintjs/fingerprintjs.
unauthenticated · 60 req/hr
A live read does not change what is printed above it. The site records that you ran it; what GitHub returned is not kept. The printed state moves only when the register is swept and a new printing is issued. raw JSON
A 301 from the source itself is the strongest liveness field there is: it is the maintainer telling you the entry moved. Nothing here is inferred. — ED.
Every other state in this register is an inference: the register observes a behaviour — a gap, a flag, a status code — and applies a printed rule to it. WITHDRAWN is the one state that is not an inference at all. A permanent redirect is the maintainer stating, in the protocol itself, that this address has been superseded and naming the address that replaced it. There is nothing to interpret.
That is why the clause is tested before any date rule. A repository can look perfectly healthy by every date field it carries and still be the wrong place to send somebody, and only the redirect knows.
Why the old entry stays in print
Nothing is deleted here when it moves. The entry keeps its name, its description, its licence field and its history, because the person who most needs this page is the one holding an old link from an old blog post, and a register that quietly removes moved entries cannot be audited against its own earlier printings.
The replacing address is printed beside the superseded one, along with the status code and the instant the check was made, so the whole chain of evidence is on the page rather than in a maintainer's memory.
Questions about the WITHDRAWN mark
Answered from the rule printed above, and from the fields it reads.
What does WITHDRAWN mean in this registry?
That the listed address answered with a permanent redirect at the field check. It is the maintainer's own statement about where the work went, recorded verbatim as a status code and a target rather than inferred from anything.
Why not just delete an entry that moved?
Because deletion loses the finding. Old links keep circulating long after the project behind them has moved, and the reader arriving on one needs to be told what happened rather than shown nothing. Nothing in this catalogue is removed when it is corrected; it is struck, and the strike is the record.
Is a 302 treated the same way as a 301?
No. Only a permanent redirect sets this state, because only a permanent redirect is a statement about where the work lives. A temporary redirect says something about right now, and this register does not turn a temporary condition into a permanent record.
Every row on this page is a project someone once chose, and the state
beside it is the part that was invisible at the moment of choosing.
Donut Browser is filed in section
01 under the same rule, with the same fields printed against it and
no exemption of any kind: an open-source anti-detect browser under
AGPL-3.0, with engine-level fingerprint spoofing through the Wayfern
Chromium fork rather than injected JavaScript, a local REST API and MCP
server on your own machine, self-hostable sync, and a pre-launch gate
that refuses to start a profile when the proxy's exit geography
contradicts the profile's fingerprint. If it stops shipping, this
rubric marks it without anyone's permission.