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

@ch1/browser-dna

v0.1.1

Published

Browser DNA is a tool for generating web browser fingerprints

Downloads

5

Readme

CH1 Browser DNA

CircleCI

This is not well maintained

Installation

yarn add @ch1/browser-dna

What is This

This is a simple browser finger print generator that focuses on the JavaScript side of browser finger printing.

For full fledged fingerprinting, server side solutions should also be used. They would look at HTTP headers, IPs, and if they have access to lower protocols even OS fingerprinting.

Morality of Browser Fingerprinting

Fingerprinting can be a hot button topic and for good reason. Privacy on the internet is an illusion. We should expect some modicum of privacy but we should also be aware of the limitations of the tools we use. This library and other - more robust - libraries like Panopticlick show just how much trivial seeming data we give away that actually "marks" us.

Ultimately your fingerprint from a library like this, in combination with an IP address is not really enough to uniquely identify most people but it really shrinks the pool, especially in certain areas.

Why Would We Want This?

While we want and should have privacy there is a strong use case for having our connections be semi-identifiable.

Consider the following:

  • You run a web service of some sort
  • You're getting a lot of connections from one IP
  • The IP represents a huge institution that has a lot of legitimate users but due to NAT they all appear as one user

This is where at least fingerprinting headers and connection detail server side helps.

Another case would be implementing an app that uses semi-anonymous sharing having a JS + server side fingerprint would allow the app to somewhat distinguish anonymous connections for the purpose of say short term chat.

Usage

import { create } from '@ch1/browser-dna';

const fingerprint = create();

// now send fingerprint to a server

The current fingerprint only includes this set:

export interface Fingerprint {
  browserDepth: number;
  browserHeight: number;
  browserWidth: number;
  concurrency: number;
  os: string;
  plugins: string[];
  tzOffset: number;
  usesTouch: boolean;
  usesCookies: boolean;
}

License

LGPL