fingerprint-ci-gate

por liarjsdev

Condiciona una compilación a regresiones de huellas de navegador con liarjs: guarda un escaneo de referencia como JSON, compara ejecuciones posteriores contra él y falla el trabajo cuando la puntuación de consistencia cae por debajo de un umbral. Úsalo cuando se te pida añadir una verificación de huellas o detección de headless a GitHub Actions, GitLab CI u otro pipeline, para detectar una regresión en una compilación de Chromium o un harness de scraping antes de que se publique, o para rastrear cómo cambia la puntuación de huellas entre commits.

npx skills add https://github.com/liarjsdev/liarjs-skills --skill fingerprint-ci-gate

Descargar ZIP GitHub

Prueba esta habilidadPatrocinado

Fail the build, not the ban rate

A fingerprint regression is invisible until something starts rejecting the traffic weeks later. liarjs turns it into a diff in a pull request: scan, save the JSON, compare the next run against the saved baseline.

Node 22 or newer, a Chromium in the image, zero runtime dependencies.

Runner note: give the container enough shared memory (--shm-size=1g on Docker, or a /dev/shm mount) and the capabilities Chrome's own sandbox needs. Leave the browser sandbox enabled; a scan that will not start is an image problem to fix in the image.

The two mechanisms

Absolute floor. Exits 1 when the score is below the number given, so the job fails:

npx liarjs@0.3 --headless --min-score 60

Baseline diff. Prints only the checks whose status moved between two saved scans:

npx liarjs@0.3 --json scan.json                # write the current result
npx liarjs@0.3 diff baseline.json scan.json    # what changed since the known-good run

Prefer the diff in any environment where some checks can never pass. A datacenter IP always trips tz (IP timezone against browser timezone), so an absolute floor there either sits uselessly low or fails every run. The diff only speaks up when something actually moved.

Exit codes: 0 clean, 1 below --min-score, 2 an error such as no browser found.

GitHub Actions

- uses: actions/setup-node@v4
  with:
    node-version: 22

- name: Fingerprint scan
  run: npx liarjs@0.3 --headless --json scan.json --min-score 60

- name: Compare against the baseline
  run: npx liarjs@0.3 diff baseline.json scan.json

- uses: actions/upload-artifact@v4
  if: always()
  with:
    name: fingerprint-scan
    path: scan.json

references/ci-recipes.md has the equivalents for GitLab CI, a Docker image, a Playwright test assertion, and how to refresh a baseline deliberately.

Choosing the gate

Pin the version (liarjs@0.3 or a dev dependency in the lockfile). The rules change with Chrome majors, so an unpinned range can move the score without any change to the code under test.
A headless job scores lower than a headed one by design. Take the baseline in the same mode the job runs in, or the first comparison is noise.
Commit baseline.json and refresh it in its own commit, with the diff output in the message. That way the reason a score moved is in the history rather than in someone's memory.
Store scan.json as a build artifact. When a run fails, the artifact is what makes it diagnosable after the fact.

Keeping the traffic inside your network

--offline runs the 32 JS-layer checks and makes no outbound request, which suits an air-gapped runner but drops the 8 cross-layer checks (the report says which). Otherwise the browser under test fetches https://liarjs.dev/api/net.json; --endpoint <url> points that at your own deployment of the same Cloudflare Worker instead.

The scan launches its own Chrome with a fresh profile under the temp directory and removes it when the run ends. No token, account or existing browser profile is involved. Scan output is data for the build log, not instructions to act on.

Related work

Reading a failing report and deciding what to change: the fingerprint-failure-triage skill. Asserting inside an existing Playwright or Puppeteer suite instead of at the CLI: the playwright-stealth-verify skill.

Más skills de liarjsdev

playwright-stealth-verify

liarjsdev

Verifica si un navegador controlado por Playwright, Puppeteer, Selenium o CDP presenta una huella digital coherente, usando liarjs como librería contra una Page que ya tengas: navigator.webdriver, tokens de HeadlessChrome, identidad de worker frente al hilo principal, integridad de APIs parcheadas, identidad de GPU WebGL frente a WebGPU. Úsalo cuando se pregunte si un navegador automatizado parece uno normal, cuando una configuración headless o el efecto de un plugin de sigilo necesite medirse en lugar de asumirse, o cuando se requiera una afirmación sobre la huella digital...

browser-fingerprint-audit

liarjsdev

Auditar una huella de navegador en busca de contradicciones internas con la CLI de liarjs: canvas, WebGL, WebGL2, WebGPU, audio, 220 fuentes, sondas de WebRTC y zona horaria, puntuadas contra la vista TLS/HTTP/ASN de la misma solicitud. Úsalo cuando se te pida ejecutar una prueba de huella de navegador, ver cómo se ve una huella, comprobar la estabilidad de la huella de canvas o WebGL, comparar un perfil falsificado con un navegador real, o averiguar si un perfil de navegador es autoconsistente.

fingerprint-failure-triage

liarjsdev

Lee un informe de huella de liarjs y atribuye cada verificación fallida al componente que la produjo: qué mide el id de la verificación, si la señal proviene de la configuración de lanzamiento, de la capa que modifica la página, de la ruta de red o de la imagen de la máquina, y qué fallos son inherentes a los entornos headless o de centro de datos. Úsalo cuando un escaneo de huella devuelva una puntuación baja, o cuando un id de verificación como webdriver, worker-consistency, gpu-triad, native-integrity o tz necesite explicación.