npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

browser-fp

v1.0.23

Published

Project Title: Increasing Confidence Score of Browser Fingerprinting

Downloads

11

Readme

Browser-FP

Project Title: Increasing Confidence Score of Browser Fingerprinting

Project Description: Over the past few years, the trend in web browsers has generally favored more privacy for users. Almost all mainstream browsers (Safari, Firefox, Brave, and Chrome) now block third-party cookies, which enable tracking across multiple sites, and Chrome uses encrypted traffic (via HTTPS) by default. More privacy is generally a good thing for legitimate users. But, increased browser privacy also comes with a hidden cost. By preventing cookies and other tracking mechanisms, it's tough for web application developers to figure out whether a visitor is an actual user or a fraudulent bot. Another way to identify users without intrusive cookies is known as Browser Fingerprinting. Browser fingerprinting can be used to identify users uniquely and their associate sessions regardless of anonymizing tactics like incognito browsing, VPNs, and cookie blockers. Unlike third-party cookies, which can be cleared or blocked by the browser, your browser fingerprint cannot be altered. Also, it maintains a confidence score of a floating-point number between 0 and 1 that represents the probability of accurate identification. The closer this number is to 1, the more sure we are that the visitor is correct. The closer it is to 0, the more uncertainty we have about the identification results. As depicted by our project title, our ultimate aim will be to increase the confidence score using Various techniques like :

  1. By implementing more and more fingerprinting methods like Canvas fingerprinting, audio fingerprinting, WebGL fingerprinting, WebRTC fingerprinting, etc., in the browsers.
  2. Deriving a solution to prevent browsers like safari, brave, etc., from preventing browser fingerprinting(decreasing confidence score, which results in failure of browser fingerprinting).
  3. By implementing invisible trackers and tracking ads in browsers, which cannot be blocked partially by the extensions already blocking some of them, thus giving us the chances to increase confidence score.
  4. Making an ML bot that detects which fingerprinting methods a particular browser is using and which all is missing. Then, notifying how to fix the missing one after implementing some more features to the fingerprinting process already implemented in that browser, thus increasing the confidence score.

Useful Blogs:

https://cdn.jsdelivr.net/npm/[email protected]/dist/src/index.js

// Initialize the agent at application startup. const fpPromise = import('https://cdn.jsdelivr.net/npm/[email protected]/dist/src/index.js') .then(FingerprintJS => FingerprintJS.load())

// Get the visitor identifier when you need it. fpPromise .then(fp => fp.get()) .then(result => { // This is the visitor identifier: const visitorId = result.visitorId console.log(visitorId) })