Habilidades fingerprint-ci-gate
📦

fingerprint-ci-gate

Revisión del contenido r1 Riesgo alto 📁 Acceso al sistema de archivos⚙️ Comandos externos🌐 Acceso a red

Add Fingerprint Regression Gates to CI

Browser fingerprint changes can silently break automated Chromium workflows. This skill adds repeatable liarjs scans, baseline comparisons, and score gates to CI pipelines.

Compatible con: Claude Codex Code(CC)
⚠️ 38 Deficiente

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente
Review the Skillstore skill "fingerprint-ci-gate" from https://skillstore.io/skills/liarjsdev-fingerprint-ci-gate.md and its manifest at https://skillstore.io/api/skills/liarjsdev-fingerprint-ci-gate/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Detalle Markdown GET /skills/liarjsdev-fingerprint-ci-gate.md Manifest firmado GET /api/skills/liarjsdev-fingerprint-ci-gate/manifest Lockfile firmado GET /api/skills/liarjsdev-fingerprint-ci-gate/lockfile

Pruébalo

Usando "fingerprint-ci-gate". Add a fingerprint gate to a GitHub Actions job.

Resultado esperado:

  • Use Node.js 22 and a version-pinned liarjs dependency.
  • Run the headless scan with a minimum score of 60.
  • Upload the scan report even when the gate fails.

Usando "fingerprint-ci-gate". Our datacenter runner always fails the timezone check.

Resultado esperado:

Use a baseline comparison from the same runner mode. Document the timezone exception instead of lowering the global score threshold.

Usando "fingerprint-ci-gate". Keep fingerprint tests inside our network.

Resultado esperado:

Use offline mode for JavaScript checks or direct the cross-layer checks to an approved self-hosted endpoint.

Auditoría de seguridad

Riesgo alto
v1 • 8/8/2026 Abrir el informe versionado

Most static alerts are false positives caused by Markdown formatting or ordinary shared-memory documentation. Confirmed risks include executing a third-party package and sending fingerprint checks to an external endpoint. The anti-detection framing can facilitate unauthorized bot evasion.

2
Archivos escaneados
212
Líneas analizadas
4
Elementos de revisión
0
Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (1)

Alto
SKILL.md:8-12SKILL.md:35-37
Anti-Bot Evasion Enablement
The skill frames fingerprint consistency as a way to avoid rejected automated traffic and detect changes that expose headless scraping harnesses.
The text explicitly links fingerprint regressions to traffic rejection and describes tuning checks for datacenter environments. This supports anti-detection use beyond ordinary compatibility testing.
Elementos de revisión de capacidades (4)

Estas son capacidades locales reales que pueden esperarse para esta habilidad, por lo que requieren revisión, pero no se cuentan como comportamiento malicioso confirmado.

Medio
SKILL.md:24-26
Ruby/shell backtick execution
```bash
The fenced example instructs users to execute a third-party npm package through npx. Version pinning reduces drift but does not remove package execution risk.
Medio
SKILL.md:30-33
Ruby/shell backtick execution
```bash
The fenced block instructs users to run liarjs through npx and process local baseline files. This executes third-party package code in the build environment.
Medio
SKILL.md:43-59
Ruby/shell backtick execution
```yaml
The YAML block contains CI steps that execute liarjs through npx and upload scan output. These are intentional external commands with package and artifact exposure risk.
Bajo
SKILL.md:79
Hardcoded URL
fetches `https://liarjs.dev/api/net.json`; `--endpoint <url>` points that at your own deployment of
The documentation states that online scans fetch a fixed external endpoint. This exposes runner network metadata and fingerprint-related request data outside the controlled environment.

Factores de riesgo

📁 Acceso al sistema de archivos (2)
references/ci-recipes.md:31 SKILL.md:16
⚙️ Comandos externos (17)
SKILL.md:11 SKILL.md:16 SKILL.md:24-26 SKILL.md:26-30 SKILL.md:30-33 SKILL.md:33-36 SKILL.md:36-39 SKILL.md:39-43 SKILL.md:43-59 SKILL.md:59-61 SKILL.md:61-66 SKILL.md:66-70 SKILL.md:70-72 SKILL.md:72-77 SKILL.md:77-79 SKILL.md:79 SKILL.md:88-90
🌐 Acceso a red (1)
SKILL.md:79
Auditado por: codex
Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado
Evaluación de seguridad

Copiar enlace del informe

https://skillstore.io/skills/liarjsdev-fingerprint-ci-gate/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Insignia Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/liarjsdev-fingerprint-ci-gate/security.svg)](https://skillstore.io/skills/liarjsdev-fingerprint-ci-gate?utm_source=security_passport_badge)

Insignia HTML

<a href="https://skillstore.io/skills/liarjsdev-fingerprint-ci-gate?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/liarjsdev-fingerprint-ci-gate/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Tarjeta para insertar

<iframe src="https://skillstore.io/embed/skills/liarjsdev-fingerprint-ci-gate.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Citas académicas (APA · BibTeX · CFF)

Cita APA

liarjsdev. (2026). fingerprint-ci-gate security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/liarjsdev-fingerprint-ci-gate/audits/1

Cita BibTeX

@techreport{liarjsdev-liarjsdev-fingerprint-ci-gate-2026, author = {liarjsdev}, title = {fingerprint-ci-gate security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/liarjsdev-fingerprint-ci-gate/audits/1}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "fingerprint-ci-gate security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "liarjsdev" date-released: "2026-08-08" url: "https://skillstore.io/skills/liarjsdev-fingerprint-ci-gate/audits/1" identifiers: - type: other value: "skillstore:liarjsdev-fingerprint-ci-gate:audit:1" description: "Skillstore immutable audit report identifier"

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio
41
Arquitectura
85
Mantenibilidad
87
Contenido
65
Comunidad
91
Cumplimiento de la especificación

Lo que puedes crear

Protect Browser Automation Builds

Add a fingerprint baseline comparison before deploying changes to a Chromium automation harness.

Standardize CI Fingerprint Checks

Create repeatable score gates and artifacts across GitHub Actions or GitLab CI.

Verify Test Browser Consistency

Assert specific fingerprint checks inside an existing Playwright suite.

Prueba estos prompts

Add a Basic Score Gate 
Add a version-pinned liarjs fingerprint check to my GitHub Actions workflow. Use Node.js 22 and fail when the score is below 60.
Compare Against a Baseline 
Create a CI workflow that saves scan.json, compares it with baseline.json, and uploads the current scan after every run.
Configure an Offline Runner 
Adapt my fingerprint gate for an air-gapped GitLab runner. Use offline mode and explain which checks are unavailable.
Design a Playwright Gate 
Add authorized fingerprint assertions to my Playwright suite. Ignore only documented environment-specific checks and prevent unrelated score changes from hiding failures.

Mejores prácticas

  • Pin liarjs with an exact version and a committed lockfile.
  • Create baselines in the same browser mode and runner environment used by CI.
  • Store scan artifacts and explain every deliberate baseline change.

Evitar

  • Do not disable the Chromium sandbox to make a container start.
  • Do not lower a global threshold to hide one environment-specific check.
  • Do not use fingerprint testing against systems without explicit authorization.

Preguntas frecuentes

What does the CI gate measure?
It measures liarjs browser fingerprint consistency and can compare individual check results with a saved baseline.
Which runtime does the skill require?
The examples require Node.js 22 or newer and a discoverable Chrome, Chromium, or Edge browser.
Should I use a score floor or a baseline?
Use a baseline when your environment has known permanent failures. Use a score floor for stable, controlled runners.
Does the scan make network requests?
Online mode contacts liarjs.dev for cross-layer checks. Offline mode skips those checks, and a self-hosted endpoint is supported.
How should I update a baseline?
Refresh it in a dedicated commit and record the observed differences and reason.
Can this run inside Playwright?
Yes. The reference shows checkPage assertions against the page and browser configuration already used by the test suite.

Detalles del desarrollador

Autor

liarjsdev

Licencia

MIT

Revisión de Skillstore

r1

Aviso de versión

El autor no declaró una versión.

Repositorio

https://github.com/liarjsdev/liarjs-skills/tree/4068c79209753c74f895a4a5a6d117fcde8d94d1/skills/fingerprint-ci-gate

Ref.

9939e94735a710f16446f189eea126372136575b

Actualidad del mantenimiento

9/8/2026

Uso

0 descargas · 0 vistas

Estructura de archivos

📁 references/

📄 ci-recipes.md

📄 SKILL.md