browser-fingerprint-auditlisted

# 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 ```bash 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. ## What a run does to the machine - Launches its own Chrome with a fresh profile in a temp directory (`mkdtemp`), then deletes that directory when the scan ends. It does not read the user's browser profile, history, cookies or saved credentials, and does not need any token or account. - Probes run on `about:blank` by default. Pass `--page <url>` only when the user na