do not rely on 0 plugins for detecting headlesschrome - #194
Open
unixfox wants to merge 1 commit into
Open
Conversation
xnerhu
approved these changes
Nov 25, 2024
Author
|
hello @xnerhu @r-valitov any update on this PR :)? I have been using on my own website and I haven't had any user complain anymore. |
osbre
added a commit
to osbre/BotD
that referenced
this pull request
Dec 18, 2025
igneel64
pushed a commit
to snowplow/snowplow-javascript-tracker
that referenced
this pull request
Aug 18, 2026
…ngth detector BotD's `detectPluginsLengthInconsistency` reports any non-Android Chromium browser with `navigator.plugins.length === 0` as headless Chrome. Chrome's `--headless=new` mode now reports plugins like a headed browser, while privacy-focused browsers legitimately report none, so the check only yields false positives. Rather than patch the dependency, compose BotD's exported `collect`/`detect` with our own detector set. A pnpm patch would only reach the UMD build, since the ESM build keeps `@fingerprintjs/botd` external and npm consumers would resolve their own unpatched copy. Mirrors fingerprintjs/BotD#194, which is approved upstream but unmerged and so absent from botd 2.0.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
igneel64
pushed a commit
to snowplow/snowplow-javascript-tracker
that referenced
this pull request
Aug 19, 2026
…ngth detector BotD's `detectPluginsLengthInconsistency` reports any non-Android Chromium browser with `navigator.plugins.length === 0` as headless Chrome. Chrome's `--headless=new` mode now reports plugins like a headed browser, while privacy-focused browsers legitimately report none, so the check only yields false positives. Rather than patch the dependency, compose BotD's exported `collect`/`detect` with our own detector set. A pnpm patch would only reach the UMD build, since the ESM build keeps `@fingerprintjs/botd` external and npm consumers would resolve their own unpatched copy. Mirrors fingerprintjs/BotD#194, which is approved upstream but unmerged and so absent from botd 2.0.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello,
I'm running BotD in production and with one of my user I diagnosed that
navigator.plugins.lengthreturns0on his browser.He is running Vivaldi 7.0.3495.18 (Stable channel) on Windows and without any extension installed the browser gives no plugins in the list:
I'm proposing to remove the classification that if the plugins list is empty, then it's a headless chrome.
First because now for
--headless=new, the value fornavigator.plugins.lengthis not empty anymore. It's5. Everyone is already using that new headless method or spoofing the value fornavigator.pluginsAnd second, the API
navigator.pluginsis no longer recommended: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/plugins. So we may run into some false positive if some browser decides to not disclose the plugins list as part of protecting the privacy of the user.