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

ubid

v0.1.2

Published

A browser identification library.

Downloads

2,037

Readme

ubid - Unique Browser ID

====

Attempts to generate a number of unique identifiers for a given browser.

These identifiers are useful for when cookies and/or local storage have been disabled. For instance, Apple has started doing this for all third-party websites shown in iframes. Although that may help privacy to some degree (arguably, not enough of a degree given this module), it can also render parts of sites unusable for legitimate purposes to users.

var ubid = require( 'ubid' );

ubid.get( function( error, signatureData ) {
    if ( error ) {
        console.error( error );
        return;
    }
    
    // dump for example
    console.log( signatureData );
} );

Would produce:

{
    "random": {
        "signature": "0d9444a0-c566-4c87-a2c6-406b2e12a26a"
    },
    "browser": {  
        "signature": "fe90bcf955cc65b51f1adc1ca374f163e09a29c6d173e25c783c9c5c77badada"
    },
    "canvas": {
        "signature": "db5991b6bb503650bf69b285a6c0f895f11b73c135c112905241f60835be2652"
    },
    "localStorage":true
}

Let's break them down:

  • random

This is a random guid assigned to the browser. This will change each time unless localStorage is true, in which case this is the best identifier to use since it is almost certainly guaranteed to be unique and to persist.

This is also a best case for private browsing modes in that this id will differ from normal browsing (this is normally desirable).

  • canvas

This is a unique id generated by rendering some fonts and colors to an HTML5 canvas and hashing the result. According to various sources (eg: https://www.browserleaks.com/canvas) this can be a fairly reliable unique identifier due to the variances in how different graphics cards and systems will render the results.

  • browser

This is a unique id generated by joining and hashing a number of browser attributes. This is most likely the least unique identifier and should be the last resort for identifing a particular user/browser.