Catch browser fingerprint regressions before they ship.
CI testing
Gates CI builds on browser fingerprint regressions using saved scans, baseline diffs, or a minimum score.
When to use it
Use when adding fingerprint or headless-detection checks to CI pipelines or tracking fingerprint scores across commits.
Give it a project; it adds a version-pinned fingerprint scan and CI gate with baseline comparison and scan artifacts.
What you provide
This skill
scan.json build artifact
Stores fingerprint scan artifacts
https://liarjs.dev/api/net.json
Fetches liarjs network data
Chrome
Launches a separate Chrome process
Chrome profile under the temp directory
Creates and removes a temp profile
Requires Node 22 or newer.
Requires a Chromium browser that the launcher can find.
The CI container needs enough shared memory; Docker is shown with a 1 GB allocation.
The runner or container must permit the capabilities required by Chrome's sandbox.