The maintainer set the archived flag. A statement from the author outranks every date rule, and it is why these are listed as historical rather than stale.
The rule that sets it, second edition:
GitHub archived flag is true.
Why ARCHIVED: archived = true, set 2025-09-28. A maintainer's own statement outranks every date rule.
Field
Value at this printing
pushed_at
—
archived
true
archived_at
2025-09-28
latest_release
—
license.spdx_id
null (none declared)
stargazers_count
163
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: GET https://api.github.com/repos/Kaliiiiiiiiii-Vinyzu/CDP-Patches
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
Archived by its own author, which is a maintainer's statement and outranks any inference from a push date. Listed as historical because the technique still explains what the protocol gives away. — ED.
Why ARCHIVED: archived = true, set 2025-05-01. A maintainer's own statement outranks every date rule.
Field
Value at this printing
pushed_at
—
archived
true
archived_at
2025-05-01
latest_release
—
license.spdx_id
BSD-3-Clause
stargazers_count
3100
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: GET https://api.github.com/repos/salesforce/ja3
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 flag is a statement, and a date is only a symptom
The archived flag is the only measured field in this rubric that outranks every date rule, and it earns that rank by being categorically different from the others. A push date is the register inferring intent from behaviour. An archive flag is the maintainer declaring intent directly. When the two disagree — and they do, because plenty of projects are archived within weeks of a healthy-looking commit — the declaration wins.
It also survives in both directions. An archived repository with a recent push is still archived. A repository quiet for four years without the flag is DEAD by the date rule, not archived, because nobody has said it is over.
What an archived project is good for
It is readable, forkable and permanently frozen. Nothing will be merged, no advisory affecting it will be answered there, and the issue tracker is a museum. That makes it genuinely valuable as a reference and a liability as a dependency, and the two uses should not be confused.
Several of the most important entries in this catalogue are here: formats whose reference implementations were archived while the formats themselves went on being spoken everywhere. Read the last push date beside the archive date, because the interval between them says a great deal about how the project ended.
Questions about the ARCHIVED mark
Answered from the rule printed above, and from the fields it reads.
What does ARCHIVED mean here?
That the repository host reports the archived flag as true. It is a maintainer's own statement rather than a measurement of silence, and this rubric tests it before any date rule for exactly that reason.
Is an archived project the same as a dead one?
No. DEAD in this register means an address that did not answer, or a repository untouched past the 1095-day outer threshold — a condition observed. ARCHIVED means somebody said it was over. The distinction matters because an archived project is frozen deliberately and a dead one may simply have been forgotten.
Can I fork an archived project listed here?
That depends entirely on its licence, not on its state, which is why the licence column sits beside the state column on every row. An archived repository with no declared licence gives you no grant at all, and the archive flag does nothing to change that.
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.