Catalogue · Section 10 · Entry
Nika-Proxy/awesome-tls-fingerprinting
ACTIVE
Nika-Proxy/awesome-tls-fingerprinting is a project catalogued in section 10 of this register. Narrow TLS-only list, vendor-operated, with no stars at the field check. It reads ACTIVE at the last field check — its most recent push was about 3 months before that check, inside the 90-day threshold the rubric in force prints.
https://github.com/Nika-Proxy/awesome-tls-fingerprinting
The fields this state was derived from
| Field | Value at this printing |
|---|---|
| pushed_at | 2026-05-19 |
| archived | false |
| latest_release | — |
| license.spdx_id | null (none declared) |
| stargazers_count | 0 |
| http_status | 200 |
| fetched_at | 2026-08-14T09:12:00Z |
| endpoint | GET https://api.github.com/repos/Nika-Proxy/awesome-tls-fingerprinting |
| rubric_edition | 2nd, in force since 2026-08-14 |
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
Why it reads ACTIVE
pushed_at = 2026-05-19 — 87 days, within the 90-day ACTIVE threshold.
Shipping. Safe to build on today.
Under the superseded first edition
Unchanged: the first edition read ACTIVE from the same fields.
The rubric in force · The superseded first edition · Errata leaf
What Nika-Proxy/awesome-tls-fingerprinting actually does
A narrow TLS-only list, operated by a proxy vendor, covering the same ground as section 07 of this catalogue and nothing else.
What Nika-Proxy/awesome-tls-fingerprinting's maintenance signals mean
The liveness field here is pushed_at, read as 2026-05-19 against a field check 87 days later. That is inside 90 days, and 90 days is where the second edition of the rubric put ACTIVE after moving it down from the first edition's 180.
The reason for the move is worth stating, because it is the kind of threshold that looks arbitrary until you know what it is measuring against: detection changes on a shorter cycle than half a year, so a six-month-old evasion is not a current one. What a recent push does not tell you is what was in it. A commit landing on a branch is not a release, not a fix, and not a test — it is evidence that somebody is still 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 Nika-Proxy/awesome-tls-fingerprinting sits in this catalogue
Nika-Proxy/awesome-tls-fingerprinting is filed in section 10, communities & competing registries, whose scope is this: Where the work is discussed, and the other lists covering this ground — listed with their own liveness fields, on the same rule as everything else. 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: lorien/awesome-web-scraping (ACTIVE), embeddinglayer/awesome-fingerprinting (ACTIVE), Zeeshanahmad4/awesome_list_of_anti_detect_browsers_apps (NRND). 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.
Its licence field is empty, and this register treats that as a finding rather than a gap — see every entry here that declares no licence. Source you can read is not source you have been granted the right to use, modify or redistribute, and an absent licence file means exactly that absence and nothing friendlier. It is also grouped with everything else the rubric marks ACTIVE.
What to settle before you adopt Nika-Proxy/awesome-tls-fingerprinting
Narrow scope is a legitimate editorial choice and vendor operation is a disclosure, not a disqualification — both are printed here as flags rather than argued about. It declares no licence.
Questions readers ask about Nika-Proxy/awesome-tls-fingerprinting
Answered from this entry's own fields, at the field check printed above and at no other instant.
Is awesome-tls-fingerprinting still maintained?
At the 2026-08-14 field check this register read pushed_at as 2026-05-19 and the archive flag as false, and the rubric in force turned those into ACTIVE. Shipping. Safe to build on today. The clause that fired is printed on this page, so you can check the arithmetic rather than take the word.
What else in this registry does the job awesome-tls-fingerprinting does?
No substitution edge is declared for this entry, which means nobody has stated one rather than that none exists. The nearest comparison available is the rest of section 10, where everything is answering roughly the same question on the same printed fields.
What licence is awesome-tls-fingerprinting under?
None is declared. That is a finding, not a formatting problem: without a licence file there is no grant to use, modify or redistribute the code, however openly it is published. Every entry here in the same position is listed together for that reason.
Where does this status come from?
From one sweep, recorded with the instant it ran. The raw fields, the endpoint they were read from, the fetch timestamp and the rubric edition in force are all printed on this page, and the same row is in the CC0 data files in JSON and CSV. Recompute the state from those columns and this page must agree with you; where it does not, the register is wrong.
The other lists in section 10 are catalogued here on the same rule as everything else, including their own licences and their own push dates, because a register that exempted its competitors would not be a register. Donut Browser is the tool the people who keep this one work on: an open-source anti-detect browser under AGPL-3.0, with a local REST API and MCP server on your own machine and no telemetry in it at all.
curl -fsSL https://donutbrowser.com/install.sh | sh
macOS (DMG, Homebrew cask donut), Windows (installer and portable), Linux (deb, rpm, AppImage, with APT and RPM repositories at repo.donutbrowser.com), and a Nix flake. Desktop only — there is no mobile build target. Ten shipped languages. Source, AGPL-3.0 · its own entry, judged by the same rubric · the keepers' disclosure.