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

tinyfingerprint

v0.0.2

Published

a minimalistic library for inline markdown: 9 features – 10 lines of code – 0 dependencies

Downloads

1

Readme

🫵 TinyFingerprint

a minimalistic, privacy-friendly library for browser fingerprinting in nodejs

modern fingerprinting methods involve complex client-side data-gathering tricks that invade users' privacy. however, in my experience simply generating a hash based on HTTP headers on the server's side is good enough for many non-nefarious purposes, like mitigating one person answering the same poll multiple times.

basically, this code looks at a bunch of data that your browser sends to a website when it's requesting a page, things like the IP address, user-agent and preferred languages. neither of them is necessarily unique to your device, but if you combine all of them, that combination becomes quite unique overall. the library then hashes all that data: it's a process that creates a random-looking string (like b5bc6964d26725b5ad085ecf4381f3b4aa797e52c4f8e7402cbc4e4c08ac593d) that on one hand stays the same if provided the same data again, but on another, it's virtually impossible to revert that process and find out eg. someone's IP address from it.

in other words, this library generates a hash allows you to identify, if a bunch of requests are likely to be coming from the same device and browser, without having to save any personal data about the user. and it's all done in a minimalistic fashion – in just a few lines of code and with zero dependencies.

usage

const { ip, fingerprint } = require('tinyfingerprint');

export default (req, res, next) => {
    console.log(ip(req));           // eg. 123.45.67.89
    console.log(fingerprint(req));  // eg. b5bc6964d26725b5ad085ecf4381f3b4aa797e52c4f8e7402cbc4e4c08ac593d
    next();
}

development

node tests.js     # run tests
node homepage.js  # regenerate homepage from readme

author & links