Browser Fingerprint Audit

Run it with `npx liarjs@0.3` and it launches a throwaway Chrome, scores the browser's fingerprint for internal contradictions, and checks those claims against what the edge saw of the same request: IP, ASN, TLS version, and HTTP version. A canvas that disagrees with the reported GPU, or a timezone that doesn't match the IP's region, drops the score. The skill runs its own temp profile, deletes it afterward, and has an `--offline` mode that makes no outbound request, which matters if you're auditing a machine you care about. The score only measures coherence. It won't tell you whether a given site will challenge the browser, since reputation and behavior aren't visible locally. The 40-check reference is worth reading before you trust a number.

skills.sh installs: 119.1K
GitHub stars: 5
last updated: Oct 26, 2026

View on GitHub

Install

$ npx -y skills add liarjsdev/liarjs-skills --skill browser-fingerprint-audit --agent claude-code

Installs into .claude/skills of the current project.

Files

Browser fingerprint audit

A browser controls its own JavaScript. It does not control the network it connects over. liarjs reads the fingerprint inside the browser, reads the TLS/HTTP/ASN view from the edge that served the request, and reports every place the two stories disagree.

Score: starts at 100, each failing check deducts its weight. 85 and above Trustworthy, 60 and above Suspicious, below that Likely spoofed / bot.

Run a scan

npx liarjs@0.3                    # launch a throwaway Chrome and scan it
npx liarjs@0.3 --all              # also list the checks that passed
npx liarjs@0.3 --offline          # JS-layer checks only, no outbound request
npx liarjs@0.3 --json scan.json   # save the full result for later comparison

Requires Node 22 or newer and a local Chrome, Chromium or Edge. No other install step: the package has zero runtime dependencies.

If no browser is found, set LIARJS_CHROME=/path/to/chrome. In a container, give it enough shared memory (--shm-size=1g) and run as a non-root user; Chrome's sandbox declines to initialise as root. Leave the sandbox enabled.