Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Identity coherence: combine claim-vs-measurement checks into one observation

Abierto
  • ¿Algo no está bien?
#98 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, javascript, nodejs, python
Área
backend, security

Línea de trabajo

This is a tracking issue for an observe-only identity-coherence-v1 observation under experimental.observations; the payload names no source files. Start from the existing WebGL and font axes shipped in v1.42.0 and the linked issues #92, #93 and #94. Done means the open JS engine and TLS family axes report agree, contradict or unknown, and the acceptance checks pass identically across the three servers. Ask a maintainer before starting, because the axes are design-heavy.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement go javascript python

Consolidates #92, #93 and #94 into one detection.

Each compares what the browser claims to be (User-Agent, platform) with one measured property. They are combined into a single identity-coherence-v1 experimental observation, where each measurement is one axis that reports agree, contradict or unknown. Unknown never counts.

It is observe-only: it is reported under experimental.observations and never changes the production score, token issuance, rate limits or any existing FCAPTCHA_EXPERIMENTAL_BLOCKING policy. Any future enforcement would be a new, separately named policy.

Axes

  • Claim model and OS axes: WebGL graphics backend (from #93) and font set. Shipped in v1.42.0.
  • JS engine axis (from #92): derive Blink/Gecko/WebKit from the math/error fingerprints plus cheap client probes.
  • TLS family axis (from #94): classify a natively computed or trusted-proxy JA4 into chromium/gecko/webkit from structural traits. Never uses client-supplied JA3.

Acceptance (carried over)

  • Honest Chrome, Edge, Firefox and Safari on desktop and mobile never contradict their claim, and the bench personas stay within budget.
  • Every iOS browser runs WebKit, so CriOS/FxiOS with a WebKit engine or TLS hello is honest.
  • A TLS-intercepting proxy classifies as unknown, not as a mismatch, and how is documented.
  • Synthetic contradicting vectors fire identically in all three servers.

Canvas readback stability (#95) is tracked separately.

Lenguaje dominante
JavaScript
Estrellas
221
Forks
23
Merge medio
18 h 50 min
PR fusionados (30 d)
42

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de WebDecoy/FCaptcha

Todos los issues de WebDecoy/FCaptcha

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.