antoinevastel / fpscanner Goto Github PK

I read your Fingerprint identification method and wrote it very well.
But there is a question I would like to ask, this method of yours does not recognize the webdriver-driven Firefox from the 48-60 version.
Is there any way to identify these versions of Firefox's webdriver?
Thank you

I found this to be an awesome tool for detection when I last needed it back in early 2019, but it seems like many of the tests are now bypassed...

Are there any plans to update with new tests?

Thanks!

The test for fingerprint.webDriver against Edge browsers fails because the User-Agent value contains the word "Chrome", its fingerprint.webDriverValue value is false, this the following line needs more consideration for Edge browsers...

https://docs.microsoft.com/en-us/microsoft-edge/web-platform/user-agent-string

I'm working with ElectronJS and noticed that BrowserView objects fail HEADCHR_CHROME_OBJ and HEADCHR_IFRAME tests. These tests are likely doing what they were intended to do. However, if the purpose of this project is to detect bots specifically, the overall test is failing since there isn't much automation which can be done with BrowserView objects (see https://electronjs.org/docs/api/browser-view#new-browserviewoptions-experimental).

Device memory check will make mistake if browser name parsed from userAgent is not 'Chrome', 'Chromium' or 'Opera'.
It's because this code:
if (fingerprint.deviceMemory !== 0 && !(BROWSER_REF === BROWSERS.CHROME && BROWSER_VERSION_REF >= 63) && !(/Opera/.test(BROWSER_REF) && BROWSER_VERSION_REF >= 50)) { // If deviceMemory != 0 and not recent Chrome or Opera testResult = INCONSISTENT;
Any other browser will lead to a inconsistent result.
e.g.
when use qq browser,
ua: "userAgent": "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.25 Safari/537.36 Core/1.70.3861.400 QQBrowser/10.7.4313.400"
memory: 8G
but memory check failed:

when runs on development , it give 3.

also I notice a article, my site not runs on https.

https://w3c.github.io/device-memory/#sec-security-considerations

Device-Memory Client Hint header and JS API will only be available to HTTPS secure contexts.