Skills fingerprint-ci-gate
📦

fingerprint-ci-gate

Content revision r1 High Risk 📁 Filesystem access⚙️ External commands🌐 Network access

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.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
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.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/liarjsdev-fingerprint-ci-gate.md Signed manifest GET /api/skills/liarjsdev-fingerprint-ci-gate/manifest Signed lockfile GET /api/skills/liarjsdev-fingerprint-ci-gate/lockfile

Test it

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

Expected outcome:

  • 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.

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

Expected outcome:

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

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

Expected outcome:

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

Security Audit

High Risk
v1 • 8/8/2026 Open versioned report

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
Files scanned
212
Lines analyzed
4
Review items
0
False positives ignored

Confirmed security concerns (1)

High
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.
Capability review items (4)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium
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.
Medium
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.
Medium
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.
Low
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.

Risk Factors

📁 Filesystem access (2)
references/ci-recipes.md:31 SKILL.md:16
⚙️ External commands (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
🌐 Network access (1)
SKILL.md:79
Audited by: codex
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

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

Markdown badge

[![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)

HTML badge

<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>

Embed card

<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>
Academic citations (APA · BibTeX · CFF)

APA citation

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

BibTeX citation

@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"

Skillstore Score

Why this score Evidence Confidence: Medium
41
Architecture
85
Maintainability
87
Content
65
Community
91
Spec Compliance

What You Can Build

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.

Try These 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.

Best Practices

  • 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.

Avoid

  • 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.

Frequently Asked Questions

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.

Developer Details

Author

liarjsdev

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

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

Ref

9939e94735a710f16446f189eea126372136575b

Maintenance freshness

8/9/2026

Usage

0 downloads · 0 views

File structure

📁 references/

📄 ci-recipes.md

📄 SKILL.md